bilpleje-fyn.dk

📜 Historical scan 2026-07-14 11:27:20 · ← Latest scan

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

bilpleje-fyn.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com and 1 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 6 April 2020 (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#

4 records 51ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	AS48854 team.blue Denmark A/S
ns4.simply.com	91.197.248.80	ns4.simply.com	AS48854 team.blue Denmark 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-12 12:45:38

www	93.191.156.218 (AS48854) (address records, no CNAME)
www vs bare domain	Same network bilpleje-fyn.dk: 94.231.103.100 (AS48854) www.bilpleje-fyn.dk: 93.191.156.218 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

548ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-09 18:33:04

Field	Value
Registrar	Simply.com A/S
Registered	2020-04-06
Expires	2027-04-30 (187d)

📋 WHOIS#

⏱️ Lookup Timing#

51ms

487ms

418ms

AAAA

475ms

TXT

8791ms

CAA

470ms

HTTPS

505ms

TLSA

98ms

SOA

45ms

MTA-STS

477ms

DNSSEC

548ms

SRV

144ms

Total

10045ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-02 02:51:54	660ms	4 NS 1 A 1 MX	🔒 Secure
2026-07-29 16:07:12	735ms	4 NS 1 A 1 MX	🔒 Secure
2026-07-27 08:50:38	3189ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 07:32:11	1962ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 07:30:42	1531ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 06:46:29	3186ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 03:52:08	2717ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-20 07:50:47	1895ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-19 06:05:44	2026ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-18 02:21:15	6960ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-16 22:56:02	10592ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-14 11:27:20 shown	10045ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-11 17:35:54	10166ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-09 05:04:39	1442ms	4 NS 0 A 0 MX	⚠️ Bogus
2026-07-02 05:48:43	1040ms	4 NS 1 A 1 MX	🔒 Secure
2026-06-24 18:46:23	796ms	4 NS 1 A 1 MX	🔒 Secure
2026-06-22 12:49:58	1139ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-19 16:39:08	2331ms	4 NS 1 A 1 MX	🔒 Secure
2026-06-16 14:35:38	486ms	4 NS 1 A 1 MX	🔒 Secure