bachling.dk

📜 Historical scan 2026-08-22 12:51:34 · ← Latest scan

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

bachling.dk is a registered .dk domain whose nameservers (ns1.nameservices.us, ns2.nameservices.us) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 27 January 2003 (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 5069ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.nameservices.us	—	—	—
ns2.nameservices.us	—	—	—

🌍 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-02 22:41:08

www	Address record (no CNAME)
Wildcard	Yes: any name under the zone resolves

🔗 TLSA / DANE#

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

🔐 DNSSEC#

5326ms

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-12 02:41:42

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2003-01-27
Expires	2027-01-31 (102d)

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

5069ms

5077ms

5059ms

AAAA

5069ms

TXT

65535ms

CAA

5074ms

HTTPS

5083ms

TLSA

16028ms

SOA

65ms

MTA-STS

5071ms

DNSSEC

5326ms

SRV

16077ms

Total

65535ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-05 22:57:46	1204ms	2 NS 0 A 0 MX	❓ Unknown
2026-10-02 22:41:08	2727ms	2 NS 1 A 1 MX	🔓 Insecure
2026-10-01 22:40:18	3320ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-30 22:38:36	2823ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-30 02:56:36	3377ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-29 02:47:45	3187ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-28 02:24:50	3194ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-27 02:01:51	2637ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-26 02:00:35	3293ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-25 01:40:16	3213ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-24 01:30:30	3399ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-21 08:29:44	10047ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-17 15:31:18	3361ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-11 07:18:54	4166ms	2 NS 1 A 1 MX	🔓 Insecure
2026-09-04 04:32:29	2710ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-30 22:01:48	3747ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-28 23:52:38	3154ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-27 17:19:43	7966ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-26 17:42:18	3424ms	2 NS 1 A 1 MX	🔓 Insecure
2026-08-23 21:55:58	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 12:51:34 shown	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 12:33:57	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 11:31:13	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:24:58	65535ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 00:19:20	65535ms	2 NS 0 A 0 MX	❓ Unknown