frokostjazz.dk

Records from scan: 2026-06-29 09:43:09  ·  604ms total  ·  last checked 2026-10-17 09:19 (unchanged)
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

frokostjazz.dk is a .dk domain served by 2 nameservers (ns1.curanet.dk, ns2.curanet.dk). It was registered on 29 March 2001 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 94.231.109.204 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   32ms

🌍 A Records#

1 records   34ms

📧 MX Records#

2 records   33ms

📧 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   133ms
TXT Record
v=spf1 include:spf.onlinemail.io ?all

✉️ SPF#

PolicyRecord (frokostjazz.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-09 13:53:34
www94.231.109.204 (AS48854) (address records, no CNAME)
www vs bare domainSame network
frokostjazz.dk: 94.231.109.204 (AS48854)
www.frokostjazz.dk: 94.231.109.204 (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#

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

🏷️ SOA#

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

📋 Registration#

WHOIS fetched 2026-10-09 17:40:13
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2001-03-29
Expires2027-03-31 (164d)
📋 WHOIS#

⏱️ Lookup Timing#

NS
32ms
A
34ms
MX
33ms
AAAA
34ms
TXT
133ms
CAA
34ms
HTTPS
32ms
TLSA
57ms
SOA
30ms
MTA-STS
25ms
DNSSEC
53ms
SRV
38ms
Total
604ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-06-29 09:43:09 shown 604ms 2 NS 1 A 2 MX 🔒 Secure
2026-06-21 03:32:18 467ms 2 NS 1 A 2 MX 🔒 Secure
2026-06-17 09:36:50 624ms 2 NS 1 A 2 MX 🔒 Secure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone