zimbo.dk

📜 Historical scan 2026-08-21 10:18:48 · ← Latest scan

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

zimbo.dk is a registered .dk domain whose nameservers (ns1.loopia.se, ns2.loopia.se) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 24 October 2024 (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 696ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.loopia.se	2a02:250:ffff::20 93.188.0.20	ns1.loopia.se ns1.loopia.se	AS39570 Loopia AB AS39570 Loopia AB
ns2.loopia.se	185.71.156.20 2a02:250:fffe::20	ns2.loopia.se ns2.loopia.se	AS215836 Loopia AB AS215836 Loopia AB

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

872ms

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-16 20:06:18

Field	Value
Registrar	ASCIO TECHNOLOGIES, CORP. DANMARK - FILIAL AF ASCIO TECHNOLOGIES, CORP. CANADA
Registered	2024-10-24
Expires	2026-10-23 (2d)

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

696ms

641ms

682ms

AAAA

667ms

TXT

2591ms

CAA

703ms

HTTPS

708ms

TLSA

470ms

SOA

239ms

MTA-STS

761ms

DNSSEC

872ms

SRV

695ms

Total

6359ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 19:34:06	2473ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-26 16:51:42	2771ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 11:03:37	5568ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 10:29:26	2039ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 10:18:48 shown	6359ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 10:01:09	11224ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 06:40:44	2831ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 02:28:33	5168ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 23:43:43	2970ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:08:43	5999ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 15:37:06	5551ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:00:47	6253ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 05:52:48	1073ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-06 17:54:10	10938ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 22:27:01	10923ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 20:27:47	1071ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 20:01:24	3336ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 19:34:52	1005ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 18:58:51	997ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 16:15:58	1075ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 15:29:08	16880ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-21 11:23:56	8705ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 07:45:08	3445ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-19 07:19:05	4653ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-17 21:11:57	4636ms	2 NS 0 A 0 MX	❓ Unknown