dindansker.dk

📜 Historical scan 2026-08-18 23:31:19 · ← Latest scan

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

dindansker.dk is a registered .dk domain whose nameservers (ns1-07.azure-dns.com, ns2-07.azure-dns.net, ns3-07.azure-dns.org and 1 more) 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#

4 records 584ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1-07.azure-dns.com	13.107.236.7 2603:1061:0:700::7	ns1-07.azure-dns.com ns1-07.azure-dns.com	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns2-07.azure-dns.net	150.171.21.7 2620:1ec:8ec:700::7	ns2-07.azure-dns.net ns2-07.azure-dns.net	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns3-07.azure-dns.org	204.14.183.7 2a01:111:4000:700::7	ns3-07.azure-dns.org ns3-07.azure-dns.org	AS8075 Microsoft Corporation AS8075 Microsoft Corporation
ns4-07.azure-dns.info	208.84.5.7 2620:1ec:bda:700::7	ns4-07.azure-dns.info ns4-07.azure-dns.info	AS8075 Microsoft Corporation AS8075 Microsoft Corporation

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

848ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ 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#

584ms

560ms

591ms

AAAA

591ms

TXT

2362ms

CAA

559ms

HTTPS

576ms

TLSA

379ms

SOA

286ms

MTA-STS

646ms

DNSSEC

848ms

SRV

629ms

Total

8164ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-24 06:49:12	3039ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 02:30:17	9888ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 02:26:45	2207ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 02:02:12	2455ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 01:24:10	2258ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 23:31:19 shown	8164ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 02:24:25	1717ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-13 18:10:15	6168ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 12:04:59	6112ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 10:43:41	2981ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 06:59:19	4620ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-08 07:08:30	3016ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-08-06 13:07:55	3059ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 16:37:48	659ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 06:23:06	672ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 02:01:26	9573ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-08 16:26:10	1803ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-04 22:13:10	2684ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-03 00:33:33	1426ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-06-24 07:08:08	1356ms	0 NS 0 A 0 MX	⚠️ Bogus
2026-06-23 22:38:49	6637ms	0 NS 0 A 0 MX	⚠️ Bogus
2026-06-23 20:04:28	1446ms	0 NS 0 A 0 MX	⚠️ Bogus
2026-06-23 16:39:34	5507ms	0 NS 0 A 0 MX	⚠️ Bogus
2026-06-21 17:52:58	7605ms	0 NS 0 A 0 MX	⚠️ Bogus
2026-06-20 13:51:14	2292ms	0 NS 0 A 0 MX	⚠️ Bogus