nautus.dk

📜 Historical scan 2026-07-02 23:09:40 · ← Latest scan

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

nautus.dk is a registered .dk domain whose nameservers (ns1.speedydns.net, ns2.speedydns.net, ns3.speedydns.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 13 October 2009 (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#

3 records 1663ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.speedydns.net	162.214.130.229	162-214-130-229.unifiedlayer.com	AS46606 Unified Layer
ns2.speedydns.net	162.214.129.84	ns20.myserverhosts.com	AS46606 Unified Layer
ns3.speedydns.net	162.214.130.229	162-214-130-229.unifiedlayer.com	AS46606 Unified Layer

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

3087ms

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-17 12:36:26

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2009-10-13
Expires	2027-10-31 (369d)

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

1663ms

1711ms

1719ms

AAAA

1909ms

TXT

7710ms

CAA

1737ms

HTTPS

1665ms

TLSA

1468ms

SOA

1713ms

MTA-STS

2155ms

DNSSEC

3087ms

SRV

1744ms

Total

14778ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-24 02:39:44	23177ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 23:22:00	38169ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 23:15:45	14597ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 23:04:52	23730ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 20:25:51	5494ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-18 20:22:18	23293ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 04:08:52	35445ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 22:25:02	39327ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 22:39:14	40492ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 20:35:11	19824ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 18:51:54	34565ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 16:21:41	35182ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-08 09:35:38	13500ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-31 19:39:36	34452ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-30 00:51:38	34317ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:59:09	5554ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 04:21:38	6357ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:41:48	28040ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 03:04:38	34546ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 02:36:43	36632ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 23:52:52	6585ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-20 11:30:07	6950ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-19 10:54:34	28329ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-18 08:54:11	5705ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-17 07:22:46	35276ms	3 NS 0 A 0 MX	❓ Unknown