web2test.dk

📜 Historical scan 2026-08-21 09:03:19 · ← Latest scan

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

web2test.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 1 March 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 386ms

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#

623ms

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-15 00:46:55

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2006-03-01
Expires	2027-03-31 (156d)

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

386ms

444ms

448ms

AAAA

462ms

TXT

1633ms

CAA

448ms

HTTPS

445ms

TLSA

197ms

SOA

264ms

MTA-STS

506ms

DNSSEC

623ms

SRV

455ms

Total

5157ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 17:15:16	2732ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-07 19:11:17	53358ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-31 16:22:56	27118ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-27 07:51:16	10152ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 10:16:38	9021ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 09:09:26	6121ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 09:03:19 shown	5157ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 08:06:52	5722ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 07:19:15	3107ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 04:59:32	27332ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 21:41:27	3082ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 07:56:01	3111ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-14 06:46:20	1514ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 05:07:35	27213ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 04:17:56	1768ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 22:40:01	28896ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 18:13:41	33335ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 22:14:52	902ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 16:07:09	8707ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 00:27:04	1566ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 22:20:17	10075ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 11:30:05	1043ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 10:42:19	1013ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 10:29:56	1415ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 10:14:51	873ms	2 NS 0 A 0 MX	❓ Unknown