2300happynews.dk

Records from scan: 2026-09-23 23:53:43 · 10037ms total · last checked 2026-10-21 16:24 (unchanged)

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

2300happynews.dk is a registered .dk domain whose nameservers (ns1.simply.com, ns2.simply.com, ns3.simply.com and 1 more) 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 our latest scan: nameservers, A/AAAA, MX, TXT, SPF, DMARC, CAA, TLSA/DANE, MTA-STS, SRV and more.

🖥️ Nameservers#

4 records 109ms

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
ns4.simply.com	91.197.248.80	ns4.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

🔗 TLSA / DANE#

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

🔐 DNSSEC#

9189ms

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#

109ms

98ms

107ms

AAAA

108ms

TXT

487ms

CAA

107ms

HTTPS

102ms

TLSA

95ms

SOA

112ms

MTA-STS

116ms

DNSSEC

9189ms

SRV

122ms

Total

10037ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-23 23:53:43 shown	10037ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-23 22:53:44	5093ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-22 19:38:50	6451ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-21 19:26:40	1343ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-20 19:19:01	4310ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-19 17:34:39	11382ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-18 17:34:01	1281ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-17 14:17:12	1436ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-16 12:39:24	10229ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-15 01:13:06	26300ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-13 21:37:54	10301ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-12 03:52:56	4545ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-11 00:38:19	1619ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-09 21:45:17	3384ms	4 NS 0 A 0 MX	❓ Unknown
2026-08-06 03:06:33	1643ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-28 15:11:16	2428ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:38:56	8999ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-26 13:06:23	6369ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:46:20	1759ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-24 12:12:18	9109ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-23 11:48:45	1517ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-22 10:39:12	1339ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-21 10:15:33	17066ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-20 08:55:12	1551ms	4 NS 0 A 0 MX	❓ Unknown
2026-07-19 05:03:15	1762ms	4 NS 0 A 0 MX	❓ Unknown