pro-ejendomoghave.dk

📜 Historical scan 2026-06-25 21:08:15  ·  ← Latest scan
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

pro-ejendomoghave.dk is a .dk domain served by 3 nameservers (ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com). It was registered on 30 June 2025 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 192.0.78.163 is hosted by Automattic, Inc (AS2635) in United States. Mail is handled by cuxeo9l65.mx.service.one. 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#

3 records   77ms

🌍 A Records#

2 records   43ms

📧 MX Records#

1 records   54ms

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

📝 TXT Records#

2 records   219ms
TXT Record
v=spf1 include:_spf.wpcloud.com ~all
v=spf1 include:_spf.wpcloud.com include:_custspf.one.com ~all

✉️ SPF#

⚠ Multiple SPF records — RFC 7208 §4.5 violation (receivers must treat this as permerror)
PolicyRecord (pro-ejendomoghave.dk)
~all (soft fail) v=spf1 include:_spf.wpcloud.com ~all
~all (soft fail) v=spf1 include:_spf.wpcloud.com include:_custspf.one.com ~all

📨 DMARC#

PolicyRecord (_dmarc.pro-ejendomoghave.dk)
p=quarantine v=DMARC1; p=quarantine;
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 04:51:36
www CNAMEpro-ejendomoghave.dk (all on pro-ejendomoghave.dk)
www vs bare domainSame network
pro-ejendomoghave.dk: 192.0.78.163 192.0.78.213 (AS2635)
www.pro-ejendomoghave.dk: 192.0.78.163 192.0.78.213 (AS2635)
WildcardNo

🔎 SPF check#

zone-wide SPF report

DNS lookups: 1/10 · policy: ~all

  • error 2 SPF records: receivers must treat that as a permanent error (RFC 7208 §4.5)

🔗 TLSA / DANE#

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

🔐 DNSSEC#

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

🏷️ SOA#

98ms
FieldValue
Serial2025112204
Primary NS (MNAME)ns1.wordpress.com
Responsible (RNAME)hostmaster@wordpress.com
Refresh14400s
Retry7200s
Expire604800s
Minimum (neg-cache TTL)300s

📋 Registration#

WHOIS fetched 2026-10-06 07:00:01
FieldValue
RegistrarONE.COM A/S
Registered2025-06-30
Expires2027-06-29 (254d)
📋 WHOIS#

⏱️ Lookup Timing#

NS
77ms
A
43ms
MX
54ms
AAAA
43ms
TXT
219ms
CAA
41ms
HTTPS
42ms
TLSA
80ms
SOA
98ms
MTA-STS
47ms
DNSSEC
117ms
SRV
136ms
Total
771ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-24 23:11:18 9553ms 3 NS 2 A 1 MX 🔓 Insecure
2026-06-25 21:08:15 shown 771ms 3 NS 2 A 1 MX 🔓 Insecure
2026-06-24 01:01:15 1186ms 0 NS 0 A 0 MX ❓ Unknown
2026-06-22 11:12:54 836ms 3 NS 2 A 1 MX 🔓 Insecure
2026-06-17 11:37:35 644ms 3 NS 2 A 1 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone