mopa.dk

📜 Historical scan 2026-08-14 01:34:57 · ← Latest scan

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

mopa.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com) do not answer for it, so it is currently a lame delegation and does not resolve. It was registered on 8 July 2025 (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 80ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.simply.com	2a02:2339:1:15c::4562:4562 91.197.248.78	ns1.simply.com ns1.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns2.simply.com	185.25.141.15 2a02:2339:4006:101::4562:4562	ns2.simply.com ns2.simply.com	AS48854 team.blue Denmark A/S AS48854 team.blue Denmark A/S
ns3.simply.com	91.197.248.79	ns3.simply.com	AS48854 team.blue Denmark 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

🧩 Web & zone#

latest probe, not this scan · checked 2026-10-08 20:18:26

www	94.231.103.172 (AS48854) (address records, no CNAME)
www vs bare domain	Same network mopa.dk: 94.231.103.172 (AS48854) www.mopa.dk: 94.231.103.172 (AS48854)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC zone can be walked (all names enumerable)
CDS / CDNSKEY	Published: key rollovers can be automated with the registry (RFC 7344/8078) 1 CDS, 1 CDNSKEY

🔗 TLSA / DANE#

✗ No TLSA records — DANE not configured for HTTPS (_443) or MX (_25)

🔐 DNSSEC#

138ms

Check	Result
Validation Status	⚠️ Bogus — the parent still publishes a DS record, but the delegated nameservers don't answer, so no signed answer can be fetched. The zone isn't serving broken signatures; it isn't serving at all.
AD Flag (resolver validates)	✗ Not set
DS Record	✓ Found
DNSKEY Record	✗ Not found
Flags	resolution failed: failure

🏷️ SOA#

✗ No SOA record found

📋 Registration#

WHOIS fetched 2026-10-03 18:48:21

Field	Value
Registrar	Simply.com A/S
Registered	2025-07-08
Expires	2027-07-07 (262d)

📋 WHOIS#

⏱️ Lookup Timing#

80ms

106ms

82ms

AAAA

81ms

TXT

411ms

CAA

93ms

HTTPS

92ms

TLSA

80ms

SOA

97ms

MTA-STS

109ms

DNSSEC

138ms

SRV

102ms

Total

1508ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-10-03 18:32:43	451ms	3 NS 1 A 1 MX	🔒 Secure
2026-09-23 16:51:19	481ms	3 NS 1 A 1 MX	🔒 Secure
2026-09-09 11:32:34	497ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-16 20:52:40	820ms	3 NS 1 A 1 MX	🔒 Secure
2026-08-15 07:48:44	1709ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-14 01:34:57 shown	1508ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-08-12 22:18:13	1554ms	3 NS 0 A 0 MX	⚠️ Bogus
2026-07-18 11:15:44	778ms	3 NS 1 A 1 MX	🔒 Secure
2026-07-17 09:59:17	679ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-14 04:45:22	919ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-12 16:46:14	712ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-10 01:51:02	783ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-08 21:04:28	9762ms	1 NS 0 A 0 MX	❓ Unknown
2026-06-26 10:24:18	593ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-24 05:33:27	968ms	0 NS 0 A 0 MX	❓ Unknown
2026-06-19 02:20:50	795ms	3 NS 1 A 1 MX	🔒 Secure
2026-06-18 07:21:02	1163ms	3 NS 1 A 1 MX	🔒 Secure