rigtrup.dk

📜 Historical scan 2026-08-17 23:42:19 · ← Latest scan

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

rigtrup.dk is a registered .dk domain whose nameservers (ns1.meganameservers.eu, ns2.meganameservers.eu, ns3.meganameservers.eu) do not answer for it, so it is currently a lame delegation and does not resolve. It 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 2216ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.meganameservers.eu	2a01:7f60:1000:2::10 91.136.8.241	ns1.meganameservers.eu ns1.meganameservers.eu	AS9115 Hostpapa UK Ltd. AS9115 Hostpapa UK Ltd.
ns2.meganameservers.eu	2a01:7f60:9980:1::10 91.136.7.21	ns2.meganameservers.eu ns2.meganameservers.eu	AS9115 Hostpapa UK Ltd. AS9115 Hostpapa UK Ltd.
ns3.meganameservers.eu	2001:1810:4000:7::10 66.175.41.102	ns3.meganameservers.eu ns3.meganameservers.eu	AS30447 Internet Names For Business Inc. AS30447 Internet Names For Business Inc.

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

2421ms

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#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

2216ms

2228ms

2197ms

AAAA

2210ms

TXT

10107ms

CAA

2180ms

HTTPS

4211ms

TLSA

1953ms

SOA

286ms

MTA-STS

2273ms

DNSSEC

2421ms

SRV

4222ms

Total

19540ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-07 16:38:44	14328ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-30 00:26:18	16076ms	3 NS 0 A 0 MX	❓ Unknown
2026-09-25 10:16:54	19686ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-24 07:24:13	19689ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-23 06:52:18	18881ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-22 06:34:46	9347ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-21 06:16:55	19601ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-20 05:53:27	20873ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-19 05:20:41	21927ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-17 23:42:19 shown	19540ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-16 17:54:34	19342ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-15 06:47:36	16417ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-13 18:12:53	20646ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-12 14:58:32	20911ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-11 08:39:55	23654ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-09 14:11:06	18582ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-07 12:26:13	19773ms	3 NS 0 A 0 MX	❓ Unknown
2026-08-02 01:48:06	16956ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-29 08:04:39	25518ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-28 01:20:50	9426ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-27 00:47:32	12672ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-26 00:10:09	8182ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-24 23:41:07	8861ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-23 21:25:57	8586ms	3 NS 0 A 0 MX	❓ Unknown
2026-07-22 21:06:36	8540ms	3 NS 0 A 0 MX	❓ Unknown