mici.dk

📜 Historical scan 2026-07-14 08:25:36 · ← Latest scan

🧟 Lame delegation ⬇ Zone File 📜 Record History ⚡ Scan Now

mici.dk is a registered .dk domain whose nameservers (ns01.one.com, ns02.one.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 14 September 2008 (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 4029ms

Nameserver	IP addresses	PTR	ASN / ISP
ns01.one.com	195.206.121.10 2001:67c:28cc::10	ns01.one.com ns01.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns02.one.com	185.10.11.10 2001:67c:3c0::10	ns02.one.com ns02.one.com	AS51468 One.com A/S AS51468 One.com 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

🔗 TLSA / DANE

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

🔐 DNSSEC

10064ms

Check	Result
Validation Status	❓ Unknown (the delegated nameservers don't answer)
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: timed out

🏷️ SOA

✗ No SOA record found

📋 Registration

WHOIS fetched 2026-10-02 12:18:09

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2008-09-14
Expires	2026-09-30 (expired)

📋 WHOIS

⏱️ Lookup Timing

4029ms

4019ms

AAAA

4029ms

TXT

12245ms

CAA

4029ms

HTTPS

4028ms

TLSA

71ms

SOA

4027ms

MTA-STS

4037ms

DNSSEC

10064ms

SRV

4030ms

Total

25343ms

🕐 Scan History

Scanned At	Duration	Records	DNSSEC
2026-10-02 08:31:10	677ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-30 12:50:10	1433ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-25 00:11:28	2803ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-24 03:26:12	1605ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 21:32:28	6113ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 21:28:56	8752ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 21:20:45	10337ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-19 20:37:46	2962ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-18 20:25:03	3452ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 19:32:49	10256ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 13:00:03	26022ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 10:30:05	10113ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 08:23:49	8688ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-10 17:12:27	894ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-05 07:36:15	53402ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-01 09:49:37	27167ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-30 01:08:40	12458ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 23:20:12	892ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 22:24:17	936ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 21:43:17	8884ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 21:14:18	2898ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-23 19:25:05	1541ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 15:48:49	2432ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 15:41:00	29222ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-20 13:06:26	1016ms	2 NS 0 A 0 MX	⚠️ Bogus