hdntnp.cfd is registered with whois.nic.cfd. We couldn't read an SSL certificate for it when we last analysed it.
What security vendors and the WOT community say about this domain.
0 of 5 protections set up
No SPF record: any server can send mail that claims to come from this domain.
—No key at the 12 common selectors we checked. A custom selector can’t be found from DNS alone.
—No DMARC policy: receivers aren’t told what to do with mail that fails SPF and DKIM.
—Forces encrypted delivery between mail servers.
—Shows the brand logo in supporting inboxes. Optional; needs DMARC enforcement.
—Read from the domain's public DNS records.
What loads and tracks visitors when the homepage opens.
Running a full browser scan of the homepage… This takes about a minute.
We couldn't read an SSL certificate on port 443 when we last analysed hdntnp.cfd. Refresh the analysis to check again.
Internet standards that make a site faster and safer.
No similar domains registered in the last 90 days.
From CubDomain's daily newly registered domains. Similar doesn't mean malicious.
Is hdntnp.cfd’s name taken on other extensions?
No reviews yet. Used hdntnp.cfd? Be the first to say how it went.
Reviews are from CubDomain users and are separate from the security verdicts above.
Common questions, answered from this report's data.
hdntnp.cfd has no community safety rating yet. We couldn't read an SSL certificate on it when we last analysed it. See Security →
hdntnp.cfd is registered through whois.nic.cfd. See WHOIS →
Raw registry data for hdntnp.cfd. May be redacted by privacy services.
The queried object does not exist: DOMAIN NOT FOUND >>> Last update of WHOIS database: 2026-10-27T10:16:20.0Z <<<
Four timed TCP connections to port 443 from CubDomain's servers.
CubDomain is not affiliated with hdntnp.cfd. Data is collected independently from public sources and some figures are estimates, provided for information only.
Spam and malware blocklists for the site's IP and mail servers.
When the site first appeared, and what has changed since.
No changes seen since we started recording on 27 Oct 2026.
Found in public certificate transparency logs.
Searching the certificate transparency logs… This can take up to a minute.