40b.dk

📜 Historical scan 2026-09-14 09:00:28 · ← Latest scan

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

40b.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 6 February 2008 (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 161ms

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#

9173ms

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-23 07:14:58

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-02-06
Expires	2027-02-28 (128d)

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

161ms

179ms

178ms

AAAA

157ms

TXT

638ms

CAA

184ms

HTTPS

163ms

TLSA

118ms

SOA

35ms

MTA-STS

173ms

DNSSEC

9173ms

SRV

186ms

Total

9959ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-21 08:56:12	1833ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-30 23:35:34	1223ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-14 09:00:28 shown	9959ms	2 NS 0 A 0 MX	❓ Unknown
2026-09-11 05:18:16	2823ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 23:19:57	2990ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 13:26:57	10181ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 13:01:19	6058ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 12:26:37	1407ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 11:38:41	38300ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 11:36:52	10287ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:06:35	4410ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 07:31:42	2692ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 03:23:55	4411ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:44:22	1084ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 12:18:57	3607ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:03:47	2900ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 16:11:38	2930ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 14:04:51	1508ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-03 04:17:49	1166ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-02 02:30:38	9233ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 23:36:20	1439ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 09:07:03	989ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 08:35:53	916ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 07:56:03	27289ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 07:34:25	869ms	2 NS 0 A 0 MX	❓ Unknown