arnelytter.dk

Records from scan: 2026-11-12 18:36:58  ·  482ms total  ·  last checked 2026-11-16 19:17 (unchanged)
Zone File Timeline & History Scan Now

arnelytter.dk is a .dk domain served by 2 nameservers (ns1.desec.io, ns2.desec.org). It was registered on 17 February 2006 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. The zone is not DNSSEC-signed, has no DMARC policy and has no IPv6 address. 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   36ms

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#

checked 2026-11-12 18:36:58
wwwNXDOMAIN
www vs bare domainNeither resolves
arnelytter.dk: no address
www.arnelytter.dk: no address
WildcardNo
Denial of existenceNSEC3 · 0 iterations · no salt RFC 9276 ✓
CDS / CDNSKEYPublished: key rollovers can be automated with the registry (RFC 7344/8078) 2 CDS, 1 CDNSKEY

TLSA / DANE#

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

DNSSEC#

107ms
CheckResult
Validation Status Insecure
AD Flag (resolver validates) Not set
DS Record Not found
DNSKEY Record Found
Flagsresolution failed: ncache nxrrset

SOA#

44ms
FieldValue
Serial2026015168
Primary NS (MNAME)get.desec.io
Responsible (RNAME)get@desec.io
Refresh86400s
Retry3600s
Expire2419200s
Minimum (neg-cache TTL)3600s

Registration#

WHOIS fetched 2026-11-06 12:30:29
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2006-02-17
Expires2031-02-28 (1564d)

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#

NS
36ms
A
31ms
MX
42ms
AAAA
31ms
TXT
195ms
CAA
32ms
HTTPS
42ms
TLSA
47ms
SOA
44ms
MTA-STS
65ms
DNSSEC
107ms
SRV
65ms
Total
482ms

Scan History#

Scanned AtDurationRecordsDNSSEC
2026-11-12 18:36:58 shown 482ms 2 NS 0 A 0 MX Insecure
2026-11-06 01:45:27 474ms 2 NS 0 A 0 MX Insecure
2026-10-30 05:39:39 434ms 2 NS 0 A 0 MX Insecure
2026-10-22 22:37:26 1075ms 2 NS 0 A 0 MX Insecure
2026-10-16 07:23:40 1249ms 2 NS 0 A 0 MX Insecure
2026-10-09 23:40:17 896ms 2 NS 0 A 0 MX Insecure
2026-10-02 08:13:39 1094ms 2 NS 0 A 0 MX Insecure
2026-09-30 08:07:00 474ms 2 NS 0 A 0 MX Insecure
2026-09-24 19:41:31 609ms 2 NS 0 A 0 MX Insecure
2026-09-23 19:19:11 591ms 2 NS 0 A 0 MX Insecure
2026-09-15 01:53:39 1484ms 2 NS 0 A 0 MX Insecure
2026-09-08 20:07:20 9506ms 2 NS 0 A 0 MX Insecure
2026-09-04 11:32:53 471ms 2 NS 0 A 0 MX Insecure
2026-08-27 20:41:11 595ms 2 NS 0 A 0 MX Insecure
2026-08-27 18:05:11 490ms 2 NS 0 A 0 MX Insecure
2026-08-21 10:15:03 9787ms 2 NS 0 A 0 MX Insecure
2026-08-14 05:34:19 687ms 2 NS 0 A 0 MX Insecure
2026-08-07 17:02:13 630ms 2 NS 0 A 0 MX Insecure
2026-07-31 05:34:49 694ms 2 NS 0 A 0 MX Insecure
2026-07-24 20:51:27 16630ms 2 NS 0 A 0 MX Insecure
2026-07-23 18:03:46 590ms 2 NS 0 A 0 MX Insecure
2026-07-21 14:32:28 16597ms 2 NS 0 A 0 MX Insecure
2026-07-16 21:15:56 8630ms 2 NS 0 A 0 MX Insecure
2026-07-11 04:07:41 719ms 2 NS 0 A 0 MX Insecure
2026-07-03 16:22:07 753ms 2 NS 0 A 0 MX Insecure