kronjagt.dk

📜 Historical scan 2026-08-07 04:12:24 · ← Latest scan

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

kronjagt.dk is a registered .dk domain whose nameservers (ns.gullestrupnet.dk, ns2.gullestrupnet.dk, ns5.gullestrupnet.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 1 April 2011 (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#

3 records 46ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.gullestrupnet.dk	82.165.189.144	gn51.gullestrupnet.dk	AS8560 IONOS SE
ns2.gullestrupnet.dk	82.165.203.134	mail51.gullestrupnet.dk	AS8560 IONOS SE
ns5.gullestrupnet.dk	82.165.124.183	—	AS8560 IONOS SE

🌍 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#

641ms

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: ncache nxdomain

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-20 19:38:39

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-04-01
Expires	2027-04-30 (191d)

🔗 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#

46ms

804ms

954ms

AAAA

99ms

TXT

595ms

CAA

109ms

HTTPS

53ms

TLSA

68ms

SOA

49ms

MTA-STS

78ms

DNSSEC

641ms

SRV

1086ms

Total

12663ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 02:33:46	9851ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-29 18:48:34	10354ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-26 18:49:19	11187ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 13:40:27	9875ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 11:43:09	20066ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 11:16:42	12328ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 09:48:19	12174ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:47:20	11423ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 07:07:51	17036ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 15:58:58	11271ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:13:14	15182ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:04:10	11175ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 03:28:52	12096ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 19:57:55	10323ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 04:12:24 shown	12663ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-03 22:12:58	11431ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 07:25:46	10715ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 16:57:25	16217ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 15:22:54	16194ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 15:08:32	16976ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 14:37:40	9394ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 14:30:13	13129ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 12:23:02	14945ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 19:46:07	17299ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 00:48:48	11014ms	3 NS 0 A 0 MX	❓ Unknown