profetkort.dk

📜 Historical scan 2026-07-08 13:12:52 · ← Latest scan

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

profetkort.dk is a registered .dk domain whose nameservers (ns1.meganameservers.eu, ns2.meganameservers.eu, ns3.meganameservers.eu) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 558ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.meganameservers.eu	2a01:7f60:1000:2::10 91.136.8.241	ns1.meganameservers.eu ns1.meganameservers.eu	AS9115 Hostpapa UK Ltd. AS9115 Hostpapa UK Ltd.
ns2.meganameservers.eu	2a01:7f60:9980:1::10 91.136.7.21	ns2.meganameservers.eu ns2.meganameservers.eu	AS9115 Hostpapa UK Ltd. AS9115 Hostpapa UK Ltd.
ns3.meganameservers.eu	2001:1810:4000:7::10 66.175.41.102	ns3.meganameservers.eu ns3.meganameservers.eu	AS30447 Internet Names For Business Inc. AS30447 Internet Names For Business Inc.

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

663ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

558ms

555ms

562ms

AAAA

561ms

TXT

2302ms

CAA

623ms

HTTPS

395ms

TLSA

8936ms

SOA

35ms

MTA-STS

866ms

DNSSEC

663ms

SRV

1013ms

Total

14258ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-29 14:52:11	17857ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-25 20:27:00	24156ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 05:07:55	19129ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 03:32:55	19031ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 03:06:01	23663ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 02:55:01	37027ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 01:19:42	21476ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 00:46:44	20070ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 17:14:40	27383ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 15:25:09	18939ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 14:57:02	29792ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 07:00:24	19578ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:39:47	30458ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 16:34:11	20435ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 16:35:01	27155ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-05 11:05:53	31345ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 10:04:24	25568ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:18:02	22058ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:09:35	11492ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 17:06:31	23311ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:20:32	20790ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 08:27:58	26919ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 03:39:53	13925ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 23:42:10	18860ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 17:47:50	20812ms	3 NS 0 A 0 MX	❓ Unknown