bilhuset-rodding.dk

📜 Historical scan 2026-08-23 04:59:32 · ← Latest scan

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

bilhuset-rodding.dk is a registered .dk domain whose nameservers (ns3.bilinfo.dk, ns4.bilinfo.dk, ns5.bilinfo.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 15 March 2005 (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 391ms

Nameserver	IP addresses	PTR	ASN / ISP
ns3.bilinfo.dk	—	—	—
ns4.bilinfo.dk	—	—	—
ns5.bilinfo.dk	—	—	—

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

1269ms

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-22 13:12:21

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2005-03-15
Expires	2027-03-31 (158d)

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

391ms

381ms

AAAA

391ms

TXT

1511ms

CAA

451ms

HTTPS

382ms

TLSA

98ms

SOA

486ms

MTA-STS

703ms

DNSSEC

1269ms

SRV

562ms

Total

7728ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-21 13:34:37	1631ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-25 15:47:59	1579ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 05:43:29	1368ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 04:59:32 shown	7728ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 04:38:15	6710ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 04:26:12	1797ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 03:27:56	6664ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 02:06:53	1471ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 20:13:08	1453ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 21:09:38	1219ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-14 02:03:18	2414ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 06:54:35	1240ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 01:23:00	10160ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 20:29:15	1371ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 12:05:14	1761ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-06 12:25:53	1220ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-30 03:51:52	2066ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 07:14:09	3033ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 06:09:33	9704ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 05:31:48	1519ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 05:16:38	2927ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 00:51:34	1139ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 00:37:23	10057ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:33:19	1365ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 14:38:32	1338ms	3 NS 0 A 0 MX	❓ Unknown