waagepetersen.dk

📜 Historical scan 2026-08-09 00:41:22 · ← Latest scan

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

waagepetersen.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 7 June 2002 (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 35ms

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#

120ms

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#

WHOIS fetched 2026-10-25 14:20:39

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2002-06-07
Expires	2027-06-30 (247d)

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

35ms

46ms

42ms

AAAA

43ms

TXT

369ms

CAA

48ms

HTTPS

48ms

TLSA

24ms

SOA

30ms

MTA-STS

75ms

DNSSEC

120ms

SRV

16065ms

Total

16644ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-04 09:01:48	1172ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-23 23:47:05	2783ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:06:28	27243ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:42:06	10218ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:26:00	5065ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:32:52	5219ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 03:00:59	10177ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:23:35	8746ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 14:47:48	1473ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 07:18:33	1013ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 01:32:17	24982ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:31:42	3164ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 00:41:22 shown	16644ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 08:14:00	833ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 11:10:11	949ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 10:41:43	10354ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 05:54:52	985ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:51:05	10093ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:24:50	8889ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 04:23:35	1083ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:37:17	10058ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 03:14:36	872ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 01:28:21	8917ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-18 21:40:20	16650ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 21:10:02	2835ms	2 NS 0 A 0 MX	❓ Unknown