lekuluent.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -134 days left3 years old
35
lekuluent.com was registered on 12 Nov 2022 via Dynadot Inc and the registry expiry is 12 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/lekuluent.com.
lekuluent.com publishes 2 nameservers. DNSSEC is not signed.
lekuluent.com has 1 IPv4 address (91.204.209.29). The geolocation database places 91.204.209.29 in Fareham, United Kingdom.
The TLS certificate from R12 is not valid (TLS 1.3).
No safety warning was recorded for lekuluent.com in the checks that ran.
Domain · RDAP/WHOIS
lekuluent.com was registered on 12 Nov 2022 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/lekuluent.com.
| Registered | since 12 Nov 2022 |
|---|---|
| Created | 12 November 2022 |
| Updated | 11 November 2025 |
| Expires | 12 November 2026 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.hostns.io, ns2.hostns.io |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/lekuluent.com |
lekuluent.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver ns1.hostns.io is published for lekuluent.com in the registration record from https://rdap.verisign.com/com/v1/domain/lekuluent.com.
Nameserver ns2.hostns.io is published for lekuluent.com in the registration record from https://rdap.verisign.com/com/v1/domain/lekuluent.com.
DNS
lekuluent.com has 1 address record, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 91.204.209.29 |
|---|---|
| AAAA | — |
| NS | ns1.hostns.io, ns2.hostns.io |
| MX | entrap-01.hostns.io (10), entrap-02.hostns.io (10), entrap-03.hostns.io (10) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at lekuluent.com is "v=spf1 ip4:91.204.209.29 ip4:109.70.148.67 +a +mx +include:relay.mailchannels.net include:spf.hostns.io include:spf.hostns.io -all".
IPv4 address 91.204.209.29 answers for lekuluent.com at resolver 1.1.1.1:53.
Mail exchanger entrap-01.hostns.io has preference 10.
Mail exchanger entrap-02.hostns.io has preference 10.
Mail exchanger entrap-03.hostns.io has preference 10.
Hosting and geo
lekuluent.com is placed in Fareham, United Kingdom by the local geolocation database (db-ip).
| Address | 91.204.209.29 |
|---|---|
| Country | United Kingdom |
| City | Fareham |
| Source | db-ip |
SSL/TLS
The certificate for lekuluent.com is not valid, with -134 days left and 3 subject alternative names. Source: tls:443.
| Issuer | R12 |
|---|---|
| Subject | *.lekuluent.com |
| Valid from | 20 March 2026 |
| Valid until | 18 June 2026 |
| Days left | -134 |
| SAN count | 3 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.lekuluent.com, lekuluent.com, www.api.lekuluent.com.
Validation result: certificate did not validate
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://lekuluent.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:01:36Z is after 2026-06-18T18:32:51Z
Security
Family DNS for lekuluent.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Fareham.
- October 2026: geo country changed from empty to United Kingdom.
Questions
Is lekuluent.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts lekuluent.com?
lekuluent.com is placed in Fareham, United Kingdom.
When does lekuluent.com expire?
lekuluent.com expires on 12 November 2026 according to https://rdap.verisign.com/com/v1/domain/lekuluent.com.
Who owns lekuluent.com?
The registry did not return a person or a company for lekuluent.com. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/lekuluent.com at 2026-10-30T14:01:36Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:01:36Z
- TLS source tls:443 at 2026-10-30T14:01:36Z
- HTTP source https://lekuluent.com/ at 2026-10-30T14:01:36Z
- Tech source not available at 2026-10-30T14:01:36Z
- Geo source db-ip at 2026-10-30T14:01:36Z
- Safety source family DNS and local lists at 2026-10-30T14:01:36Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.