anthogenol.dk

📜 Historical scan 2026-08-19 09:59:57 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Timeline & History ⚡ Scan Now

anthogenol.dk is a registered .dk domain whose nameservers (ns1.typify.nl, ns2.typify.nl) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 22 January 2016 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Below are all of its DNS records from this scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 671ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.typify.nl	195.135.195.195 2a01:7c8:dddd:195::195	ns0.transip.net ns0.transip.net	AS20857 Signet B.V. AS20857 Signet B.V.
ns2.typify.nl	195.8.195.195 2a01:7c8:7000:195::195	ns1.transip.nl ns1.transip.nl	AS20857 Signet B.V. AS20857 Signet B.V.

🌍 A Records#

🌍

No A records found

📧 MX Records#

📧

No MX records found

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

📝

No TXT records found

✉️ SPF#

✗ No SPF record — mail spoofing not restricted

📨 DMARC#

✗ No DMARC record — mail spoofing not restricted

📬 MTA-STS#

✗ No MTA-STS policy — SMTP TLS not enforced

📈 TLSRPT#

✗ No TLSRPT record — no SMTP TLS failure reporting

📜 CAA Records#

✗ No CAA records — any CA may issue certificates

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

1167ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✗ Not found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-18 16:34:41

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2016-01-22
Expires	2027-01-31 (104d)

🔗 Same registrant#

0 domains

Other .dk domains whose WHOIS registrant has the same name and postal address. Matched on a keyed hash: the registrant's details are not stored or shown. Covers only domains whose WHOIS we have fetched (refreshed about monthly).

No other domain with this registrant in our WHOIS data yet

📋 WHOIS#

⏱️ Lookup Timing#

671ms

684ms

711ms

AAAA

1248ms

TXT

2785ms

CAA

661ms

HTTPS

668ms

TLSA

438ms

SOA

80ms

MTA-STS

1084ms

DNSSEC

1167ms

SRV

1226ms

Total

7674ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-08 19:33:52	4797ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-25 04:06:33	4162ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:48:03	5490ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 14:44:27	2032ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 14:14:37	4139ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 13:52:25	4245ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 09:59:57 shown	7674ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 09:57:44	11634ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 02:00:25	3754ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:16:26	5477ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 17:48:25	11652ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 17:08:16	11639ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 20:25:09	1876ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 12:14:44	3650ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 01:32:37	1829ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 23:30:11	11692ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 12:34:59	6462ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 12:13:22	10266ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 11:49:45	2442ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 11:11:19	10481ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:37:01	4999ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 08:28:11	4917ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 07:54:31	4268ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 04:36:58	2553ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 13:04:20	3767ms	2 NS 0 A 0 MX	❓ Unknown