birgerh.dk

📜 Historical scan 2026-08-12 17:45:51 · ← Latest scan

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

birgerh.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) 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 476ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	AS48854 team.blue Denmark A/S

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

1048ms

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#

476ms

458ms

790ms

AAAA

522ms

TXT

2048ms

CAA

458ms

HTTPS

538ms

TLSA

293ms

SOA

210ms

MTA-STS

680ms

DNSSEC

1048ms

SRV

914ms

Total

6259ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 15:41:00	1481ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-09-29 17:48:05	1808ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-27 13:40:07	1496ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 14:41:26	10152ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 14:12:24	5272ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 14:06:59	6622ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 14:03:32	2158ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 06:40:09	3333ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 06:13:53	9158ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 01:03:38	1514ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 12:10:54	3122ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 17:45:51 shown	6259ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 17:12:35	4328ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 10:35:07	1531ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-09 08:38:58	10304ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-05 20:31:15	1500ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-28 16:43:04	10399ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 13:39:13	9388ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 13:30:03	2287ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 13:11:21	9570ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 13:02:21	9382ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 12:27:48	1307ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 10:43:06	10045ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 00:45:00	9669ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-19 20:01:07	2533ms	3 NS 0 A 0 MX	⚠️ Bogus