hejdi.dk

📜 Historical scan 2026-06-17 11:11:29  ·  ← Latest scan
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

hejdi.dk is a .dk domain served by 4 nameservers (ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com and 1 more). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 34.88.65.220 is hosted by Google LLC (AS396982) in Finland. Mail is handled by smtp.google.com. The zone is not DNSSEC-signed, publishes a 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#

4 records   60ms

🌍 A Records#

1 records   73ms

📧 MX Records#

1 records   65ms

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

2 records   174ms
TXT Record
google-site-verification=tLYPwX1NBYKgJ7rTqgZT8TG5ED-ZPYfZlUbVaqk4qwU
v=spf1 include:spf.wootemple.com include:sendgrid.net include:_spf.google.com ?all

✉️ SPF#

PolicyRecord (hejdi.dk)
?all (neutral) v=spf1 include:spf.wootemple.com include:sendgrid.net include:_spf.google.com ?all

📨 DMARC#

PolicyRecord (_dmarc.hejdi.dk)
p=none (monitor only) v=DMARC1; p=none

📬 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 01:23:43
www CNAMEhejdi.dk (all on hejdi.dk)
www vs bare domainSame network
hejdi.dk: 34.88.65.220 (AS396982)
www.hejdi.dk: 34.88.65.220 (AS396982)
WildcardNo

✍️ DKIM keys#

1 found
SelectorCNAMEKey
mail — RSA · ~1024 bit below 2048 bit

DKIM selectors can't be listed, so we check the common ones (Microsoft 365, Google, Mailchimp, SendGrid, generic). Keys under other selectors aren't shown.

🔎 SPF check#

zone-wide SPF report

DNS lookups: 4/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#

84ms
CheckResult
Validation Status🔓 Insecure
AD Flag (resolver validates)✗ Not set
DS Record✗ Not found
DNSKEY Record✗ Not found
Flagsunsigned answer

🏷️ SOA#

49ms
FieldValue
Serial1
Primary NS (MNAME)ns-cloud-a1.googledomains.com
Responsible (RNAME)cloud-dns-hostmaster@google.com
Refresh21600s
Retry3600s
Expire259200s
Minimum (neg-cache TTL)300s

📋 Registration#

✗ No registration data yet — queued for a WHOIS lookup
📋 WHOIS#

⏱️ Lookup Timing#

NS
60ms
A
73ms
MX
65ms
AAAA
47ms
TXT
174ms
CAA
71ms
HTTPS
68ms
TLSA
166ms
SOA
49ms
MTA-STS
70ms
DNSSEC
84ms
SRV
0ms
Total
784ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-08 01:23:43 667ms 4 NS 1 A 1 MX 🔓 Insecure
2026-09-30 10:07:01 755ms 4 NS 1 A 1 MX 🔓 Insecure
2026-09-16 16:03:14 9591ms 4 NS 1 A 1 MX 🔓 Insecure
2026-06-17 11:11:54 1091ms 4 NS 1 A 1 MX 🔓 Insecure
2026-06-17 11:11:29 shown 784ms 4 NS 1 A 1 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone