næmt.dk xn--nmt-yla.dk

📜 Historical scan 2026-08-27 14:01:58 · ← Latest scan

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

næmt.dk is a registered .dk domain whose nameservers (ns.dandomain.dk, ns2.dandomain.dk) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 4 October 2026 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. On 7 October 2026 we saw it transfer from DANDOMAIN A/S to CURANET A/S. 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 79ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.dandomain.dk	185.25.141.3 2a02:2339:4006:109::dd	ns.dandomain.dk ns.dandomain.dk	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.dandomain.dk	2a02:2339:1:108::dd:dd 91.197.248.66	ns2.dandomain.dk ns2.dandomain.dk	AS48854 team.blue Denmark A/S 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-07 14:52:40

www	93.191.156.33 (AS48854) (address records, no CNAME)
www vs bare domain	Same network næmt.dk: 93.191.156.33 (AS48854) www.næmt.dk: 93.191.156.33 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEY	None 0 CDS, 0 CDNSKEY

🔗 TLSA / DANE#

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

🔐 DNSSEC#

168ms

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-07 15:07:30

Field	Value
Registrar	CURANET A/S
Registered	2026-10-04
Expires	2027-10-03 (344d)

📋 WHOIS#

⏱️ Lookup Timing#

79ms

87ms

83ms

AAAA

99ms

TXT

342ms

CAA

90ms

HTTPS

87ms

TLSA

62ms

SOA

43ms

MTA-STS

140ms

DNSSEC

168ms

SRV

99ms

Total

1110ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 14:52:39	1729ms	2 NS 1 A 0 MX	🔒 Secure
2026-10-05 08:46:10	118ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-02 20:18:39	165ms	1 NS 0 A 0 MX	❓ Unknown
2026-10-01 20:17:10	603ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-30 20:11:44	224ms	1 NS 0 A 0 MX	❓ Unknown
2026-09-29 20:07:28	789ms	1 NS 0 A 0 MX	❓ Unknown
2026-08-27 14:01:58 shown	1110ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-08-24 19:01:44	8685ms	2 NS 0 A 0 MX	⚠️ Bogus
2026-07-04 16:30:13	2374ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-25 07:23:09	1093ms	2 NS 1 A 0 MX	⚠️ Bogus
2026-06-24 22:07:58	349ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-20 05:23:24	799ms	2 NS 1 A 0 MX	🔒 Secure
2026-06-17 12:58:47	1310ms	2 NS 1 A 0 MX	🔒 Secure