autoget.dk

📜 Historical scan 2026-08-13 19:26:10 · ← Latest scan

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

autoget.dk is a registered .dk domain whose nameservers (ns1.netim.net, ns2.netim.net, ns3.netim.net) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 29 October 2023 (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 1512ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.netim.net	198.50.216.33	ns1.netim.net	AS16276 OVH SAS
ns2.netim.net	192.174.68.97 2001:67c:1bc::97	ns2.netim.net ns2.netim.net	AS1921 ipcom GmbH AS1921 ipcom GmbH
ns3.netim.net	176.97.158.97 2001:67c:10b8::97	ns3.netim.net ns3.netim.net	AS207021 ipcom GmbH AS1921 ipcom GmbH

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

1753ms

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 03:57:04

Field	Value
Registrar	NETIM
Registered	2023-10-29
Expires	2026-10-28 (11d)

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

1512ms

1493ms

1533ms

AAAA

1500ms

TXT

6441ms

CAA

1461ms

HTTPS

1508ms

TLSA

1207ms

SOA

374ms

MTA-STS

1624ms

DNSSEC

1753ms

SRV

1557ms

Total

14802ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 22:31:08	8759ms	3 NS 0 A 0 MX	❓ Unknown
2026-10-01 00:08:03	9838ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-27 00:35:08	14604ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 12:00:32	18928ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 07:32:08	10239ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 07:24:34	14662ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 07:14:42	15706ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 06:55:58	15206ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 04:43:38	12379ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 22:40:15	10212ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 15:00:19	3313ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:00:44	14784ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 19:26:10 shown	14802ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 13:56:50	10278ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-10 21:50:03	10449ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 14:56:14	10200ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-05 20:49:25	10237ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 03:10:19	10219ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 17:49:16	14638ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 17:14:29	2562ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-25 16:59:57	10497ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 16:45:03	2884ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 15:49:53	11436ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 14:43:19	2638ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-21 09:28:20	3049ms	3 NS 0 A 0 MX	❓ Unknown