nepu.to
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
20
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
20
nepu.to was registered on 3 Feb 2023 via NAMECHEAP and the registry expiry is 3 Feb 2028. WHOIS data came from RDAP at https://rdap.tonicregistry.to/rdap/domain/nepu.to.
No safety warning was recorded for nepu.to in the checks that ran.
nepu.to was registered on 3 Feb 2023 via NAMECHEAP. The registry returned 2 status values and 2 nameservers from https://rdap.tonicregistry.to/rdap/domain/nepu.to.
| Registered | since 3 Feb 2023 |
|---|---|
| Created | 3 February 2023 |
| Updated | 2 September 2026 |
| Expires | 3 February 2028 |
| Registrar | NAMECHEAP |
| Status | client hold, client transfer prohibited |
| Nameservers | amit.ns.cloudflare.com, love.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.tonicregistry.to/rdap/domain/nepu.to |
nepu.to carries the status "client hold". The registrar has put the name on hold. Resolvers may stop answering it while the hold lasts.
nepu.to 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 amit.ns.cloudflare.com is published for nepu.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/nepu.to.
Nameserver love.ns.cloudflare.com is published for nepu.to in the registration record from https://rdap.tonicregistry.to/rdap/domain/nepu.to.
nepu.to has 0 address records, 0 mail exchangers and 0 nameservers, measured at 1.1.1.1:53.
| A | — |
|---|---|
| AAAA | — |
| NS | — |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
Geolocation for nepu.to is not available. No local city or ASN database is installed, so this report does not guess a country.
| Geolocation | not available |
|---|---|
| Source | maxmind |
No TLS certificate was read for nepu.to on port 443.
| Available | no |
|---|---|
| Source | tls:443 |
dial tcp: lookup nepu.to on 46.38.252.230:53: no such host
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://nepu.to/": dial tcp: lookup nepu.to on 46.38.252.230:53: no such host
Family DNS for nepu.to 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.
Availability 0 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 0 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.
First checked on 30 October 2026; changes will appear here.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
The host network is not available without a local geolocation database.
nepu.to expires on 3 February 2028 according to https://rdap.tonicregistry.to/rdap/domain/nepu.to.
The registry did not return a person or a company for nepu.to. RDAP often redacts the registrant. The registrar on file is NAMECHEAP.
No other indexable reports share this TLD, host, or registrar yet.
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.
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.