birgittesaugmann.dk

📜 Historical scan 2026-09-24 01:04:32 · ← Latest scan

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

birgittesaugmann.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 29 January 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#

2 records 2129ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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#

9179ms

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

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-24 20:30:28

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2011-01-29
Expires	2027-01-31 (95d)

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

2129ms

4034ms

2127ms

AAAA

2122ms

TXT

2638ms

CAA

2125ms

HTTPS

2130ms

TLSA

121ms

SOA

2031ms

MTA-STS

2136ms

DNSSEC

9179ms

SRV

4043ms

Total

14124ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 12:00:27	2263ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-01 07:26:40	1454ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-29 22:41:46	1291ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-29 15:29:13	2530ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-24 01:04:32 shown	14124ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 08:53:14	10227ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 02:34:29	28073ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 02:30:29	6472ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 02:28:07	10157ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 00:46:36	1058ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 22:34:20	4541ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 09:56:11	917ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-15 16:08:40	8764ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 05:03:04	1787ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 17:36:40	905ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-11 08:36:18	2897ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 02:46:06	3612ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-07 11:28:11	2475ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-30 08:54:34	3121ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-29 02:30:55	2911ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 21:05:47	1443ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 20:22:18	1028ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 19:31:56	8607ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 18:53:37	10032ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 18:05:36	27295ms	2 NS 0 A 0 MX	❓ Unknown