getspace.dk

📜 Historical scan 2026-07-19 12:46:47 · ← Latest scan

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

getspace.dk is a registered .dk domain whose nameservers (ns1.netim.net, ns2.netim.net, ns3.netim.net and 2 more) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 30 August 2018 (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#

5 records 202ms

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
ns4.netim.net	—	—	—
ns5.netim.net	—	—	—

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

432ms

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-12 22:35:08

Field	Value
Registrar	NETIM
Registered	2018-08-30
Expires	2027-08-31 (315d)

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

202ms

466ms

180ms

AAAA

194ms

TXT

3011ms

CAA

190ms

HTTPS

301ms

TLSA

346ms

SOA

12ms

MTA-STS

278ms

DNSSEC

432ms

SRV

1368ms

Total

4984ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-01 05:14:00	9708ms	5 NS 0 A 0 MX	❓ Unknown
2026-09-24 10:40:56	9828ms	5 NS 0 A 0 MX	❓ Unknown
2026-09-03 02:09:17	10174ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-23 01:34:28	3484ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-22 01:26:07	10214ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-21 01:21:22	15376ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-19 23:14:05	12525ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-18 22:36:23	4460ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-17 11:40:02	10779ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-16 07:47:04	13272ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-14 22:08:05	12334ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:10:00	10223ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-12 17:59:42	11405ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-10 20:42:00	14900ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-09 15:16:38	7654ms	5 NS 0 A 0 MX	❓ Unknown
2026-08-07 13:17:44	15132ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-28 04:39:00	4499ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-27 04:12:14	3936ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-26 03:50:19	5662ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-25 03:32:54	4477ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-24 01:41:59	4425ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-22 21:36:50	4300ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-21 20:47:05	10219ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-20 15:48:20	9589ms	5 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:46:47 shown	4984ms	5 NS 0 A 0 MX	❓ Unknown