112news.dk

📜 Historical scan 2026-06-16 12:33:28 · ← Latest scan

⬇ Zone File 📜 Timeline & History ⚡ Scan Now

112news.dk is a .dk domain served by 2 nameservers (ns1.curanet.dk, ns2.curanet.dk). It was already in the .dk zone when our tracking began on 16 June 2026. The zone is DNSSEC-signed and validates, has no DMARC policy and has no IPv6 address. 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#

2 records 113ms

Nameserver	IP addresses	PTR	ASN / ISP
ns1.curanet.dk	—	—	—
ns2.curanet.dk	—	—	—

🌍 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-09 18:58:40

www	212.27.7.142 (AS44034) (address records, no CNAME)
www vs bare domain	Same network 112news.dk: 212.27.7.142 (AS44034) www.112news.dk: 212.27.7.142 (AS44034)
Wildcard	Yes: any name under the zone resolves
Denial of existence	NSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEY	None 0 CDS, 0 CDNSKEY

🔗 TLSA / DANE#

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

🔐 DNSSEC#

299ms

Check	Result
Validation Status	🔒 Secure
AD Flag (resolver validates)	✓ Set
DS Record	✓ Found
DNSKEY Record	✓ Found
Flags	resolution failed: ncache nxrrset

🏷️ SOA#

101ms

Field	Value
Serial	2025070804
Primary NS (MNAME)	ns1.curanet.dk
Responsible (RNAME)	hostmaster@curanet.dk
Refresh	14400s
Retry	3600s
Expire	1209600s
Minimum (neg-cache TTL)	300s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup

📋 WHOIS#

⏱️ Lookup Timing#

113ms

123ms

92ms

AAAA

105ms

TXT

305ms

CAA

91ms

HTTPS

80ms

TLSA

111ms

SOA

101ms

MTA-STS

111ms

DNSSEC

299ms

SRV

0ms

Total

828ms

🕐 Scan History#

Scanned At	Duration	Records	DNSSEC
2026-09-30 12:46:39	398ms	2 NS 1 A 0 MX	🔒 Secure
2026-09-28 09:06:09	525ms	2 NS 1 A 0 MX	🔒 Secure
2026-08-12 21:53:29	761ms	2 NS 1 A 0 MX	🔒 Secure
2026-08-08 02:59:46	690ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-31 17:29:11	797ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-28 23:14:13	2629ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-27 13:44:09	2740ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-26 12:44:32	625ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-25 12:20:29	2687ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-24 11:06:27	660ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-23 10:25:58	721ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-22 05:29:28	866ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-20 21:50:30	617ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-19 12:52:59	8589ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-18 09:24:35	2186ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-16 16:38:51	8729ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-14 06:55:00	588ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-12 18:41:08	782ms	1 NS 0 A 0 MX	❓ Unknown
2026-07-08 23:45:56	911ms	1 NS 0 A 0 MX	❓ Unknown
2026-06-16 12:33:28 shown	828ms	2 NS 0 A 0 MX	🔒 Secure