legalprint.dk

Records from scan: 2026-08-27 12:46:00 · 10226ms total · last checked 2026-10-20 01:46 (unchanged)

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

legalprint.dk is a registered .dk domain whose nameservers (ns.fastname.no, ns2.fastname.no) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 March 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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

2 records 223ms

Nameserver	IP addresses	PTR	ASN / ISP
ns.fastname.no	195.206.121.12 2001:67c:28cc::12	ns01.no.brand.one.com ns01.no.brand.one.com	AS197495 One.com A/S AS197495 One.com A/S
ns2.fastname.no	185.10.11.12 2001:67c:3c0::12	ns02.no.brand.one.com ns02.no.brand.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#

9192ms

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-14 02:44:57

Field	Value
Registrar	Punktum dk A/S (direct)
Registered	2018-03-08
Expires	2027-03-31 (161d)

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

223ms

280ms

157ms

AAAA

149ms

TXT

681ms

CAA

152ms

HTTPS

221ms

TLSA

119ms

SOA

58ms

MTA-STS

182ms

DNSSEC

9192ms

SRV

230ms

Total

10226ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-08-27 12:46:00 shown	10226ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-23 17:52:36	27361ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-22 15:01:19	1579ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-21 14:41:59	4747ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-20 14:32:27	1554ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-19 14:13:22	1447ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-18 14:11:09	3163ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-16 06:33:16	3791ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-15 02:51:14	4522ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:13:53	10273ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-12 19:49:10	28930ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-10 22:32:28	1519ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-09 21:41:06	2960ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-07 11:00:04	3469ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-05 03:05:31	17399ms	2 NS 0 A 0 MX	❓ Unknown
2026-08-04 01:14:54	1178ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-31 22:32:24	8753ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-29 20:01:04	2638ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-28 17:39:04	10120ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:09:12	1095ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:01:37	4326ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:46:23	1558ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-24 12:37:07	9023ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:11:12	30019ms	2 NS 0 A 0 MX	❓ Unknown
2026-07-22 04:01:16	3105ms	2 NS 0 A 0 MX	❓ Unknown