dengladekrop.dk

Records from scan: 2026-10-03 11:38:16  ·  620ms total  ·  last checked 2026-10-16 13:07 (unchanged)
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

dengladekrop.dk is a .dk domain served by 2 nameservers (ns1.curanet.dk, ns2.curanet.dk). It was registered on 14 July 2005 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 185.21.41.186 is hosted by team.blue Denmark A/S (AS48854) in Denmark. Mail is handled by mx1.onlinemail.io, mx2.onlinemail.io. The zone is DNSSEC-signed and validates, 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#

1 records   43ms

📧 MX Records#

2 records   61ms

📧 Autodiscover / Autoconfig#

ServiceCNAME / IP
🔷 Autodiscoverautodiscover-mf.onlinemail.io → 185.21.40.62
🔶 Autoconfigautoconfig-mf.onlinemail.io → 185.21.40.62

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

1 records   151ms
TXT Record
v=spf1 include:spf.onlinemail.io ?all

✉️ SPF#

PolicyRecord (dengladekrop.dk)
?all (neutral) v=spf1 include:spf.onlinemail.io ?all

📨 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-10-08 12:25:55
www185.21.41.186 (AS48854) (address records, no CNAME)
www vs bare domainSame network
dengladekrop.dk: 185.21.41.186 (AS48854)
www.dengladekrop.dk: 185.21.41.186 (AS48854)
WildcardYes: any name under the zone resolves
Denial of existenceNSEC3 · 1 iteration · 1-byte salt RFC 9276 recommends 0 iterations and no salt
CDS / CDNSKEYNone 0 CDS, 0 CDNSKEY

🔎 SPF check#

zone-wide SPF report

DNS lookups: 3/10 · policy: ?all

  • warn "?all" is neutral: it gives receivers no guidance, much like having no SPF

🔗 TLSA / DANE#

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

🔐 DNSSEC#

95ms
CheckResult
Validation Status🔒 Secure
AD Flag (resolver validates)✓ Set
DS Record✓ Found
DNSKEY Record✓ Found
Flagsfully validated

🏷️ SOA#

31ms
FieldValue
Serial2021111801
Primary NS (MNAME)ns1.curanet.dk
Responsible (RNAME)hostmaster@curanet.dk
Refresh14400s
Retry3600s
Expire1209600s
Minimum (neg-cache TTL)300s

📋 Registration#

WHOIS fetched 2026-10-07 20:03:14
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2005-07-14
Expires2027-07-31 (287d)
📋 WHOIS#

⏱️ Lookup Timing#

NS
36ms
A
43ms
MX
61ms
AAAA
55ms
TXT
151ms
CAA
44ms
HTTPS
35ms
TLSA
99ms
SOA
31ms
MTA-STS
73ms
DNSSEC
95ms
SRV
71ms
Total
620ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-03 11:38:16 shown 620ms 2 NS 1 A 2 MX 🔒 Secure
2026-07-04 20:51:29 1379ms 2 NS 1 A 2 MX 🔒 Secure
2026-06-22 22:07:52 707ms 2 NS 1 A 2 MX ⚠️ Bogus
2026-06-17 01:50:04 702ms 2 NS 1 A 2 MX 🔒 Secure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone