basmiddag.dk

📜 Historical scan 2026-07-29 06:56:31 · ← Latest scan

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

basmiddag.dk is a registered .dk domain whose nameservers (ns1.webglobe.dk, ns2.webglobe.dk, ns3.webglobe.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 3 July 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#

3 records 4032ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.webglobe.dk	195.249.159.75	—	AS3292 TDC Holding A/S
ns2.webglobe.dk	93.191.155.201	—	AS48854 team.blue Denmark A/S
ns3.webglobe.dk	85.114.133.64	—	AS24961 WIIT AG

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

10066ms

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: timed out

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-14 05:35:54

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

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

4032ms

4030ms

AAAA

4030ms

TXT

20130ms

CAA

4029ms

HTTPS

4029ms

TLSA

2024ms

SOA

4028ms

MTA-STS

4040ms

DNSSEC

10066ms

SRV

4034ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-27 17:17:03	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-03 13:12:38	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-27 14:44:00	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:10:53	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:41:09	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:13:22	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 04:30:08	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:03:20	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 14:39:24	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 18:30:40	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:45:03	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:06:52	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 15:56:53	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 20:36:51	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 09:07:14	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 16:21:30	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 06:56:31 shown	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 00:04:08	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 23:34:00	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 23:31:43	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:20:35	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 18:46:40	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 16:56:16	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 13:48:57	65535ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:59:13	65535ms	3 NS 0 A 0 MX	❓ Unknown