0mhz.dk

Records from scan: 2026-10-09 05:25:32 · 2627ms total · last checked 2026-10-16 16:10 (unchanged)

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

0mhz.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 3 August 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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 113ms

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#

144ms

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-14 16:31:23

Field	Value
Registrar	CURANET A/S
Registered	2005-08-03
Expires	2027-08-31 (318d)

📋 WHOIS#

⏱️ Lookup Timing#

113ms

118ms

164ms

AAAA

168ms

TXT

630ms

CAA

182ms

HTTPS

153ms

TLSA

113ms

SOA

34ms

MTA-STS

125ms

DNSSEC

144ms

SRV

2036ms

Total

2627ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-09 05:25:32 shown	2627ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-10-01 05:19:36	1397ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-09-26 12:14:16	10023ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-27 18:12:39	10439ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-24 04:03:09	3485ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-23 02:44:11	17403ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-22 02:39:00	1530ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-21 02:16:07	1446ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-20 01:13:36	27200ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:06:06	2968ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-17 20:22:36	10155ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-16 02:23:31	4179ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 07:17:15	27358ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 20:10:47	26892ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 23:43:56	3288ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-07 07:17:51	834ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-01 23:12:58	8639ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-29 02:52:43	2555ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-28 02:24:50	10028ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-27 02:06:45	858ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-26 01:49:11	1000ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-25 01:33:39	1029ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-24 01:02:02	9161ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-22 23:59:02	1144ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-21 16:09:49	1330ms	2 NS 0 A 0 MX	⚠️ Bogus