2change.dk

📜 Historical scan 2026-08-03 14:40:41 · ← Latest scan

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

2change.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 3 December 2006 (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 85ms

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#

167ms

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-13 01:34:18

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-12-03
Expires	2026-12-31 (70d)

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

85ms

103ms

79ms

AAAA

107ms

TXT

369ms

CAA

83ms

HTTPS

66ms

TLSA

68ms

SOA

50ms

MTA-STS

60ms

DNSSEC

167ms

SRV

154ms

Total

956ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 05:02:04	1529ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-26 06:32:30	49171ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-13 04:10:41	2789ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-02 23:44:34	27254ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-24 01:02:44	4066ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:15:31	10214ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:12:28	2012ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:03:44	2193ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 22:21:29	1532ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 21:30:34	4972ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 10:29:19	2861ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 05:37:38	2935ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 00:36:46	2831ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:42:45	9042ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 10:28:40	1379ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 18:18:46	8881ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 14:40:41 shown	956ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 19:12:19	30077ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 22:39:40	912ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:55:21	8737ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:26:03	1438ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 22:45:00	899ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 22:25:06	2108ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:49:47	10021ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 20:55:13	10121ms	2 NS 0 A 0 MX	❓ Unknown