teaterbloom.dk

Records from scan: 2026-09-29 23:22:52  ·  342ms total  ·  last checked 2026-10-16 18:32 (unchanged)
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

teaterbloom.dk is a .dk domain served by 2 nameservers (ns1.curanet.dk, ns2.curanet.dk). It was registered on 25 November 2020 (WHOIS) and was already in the .dk zone when our tracking began on 16 June 2026. Its website address 185.21.41.231 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   34ms

🌍 A Records#

1 records   30ms

📧 MX Records#

2 records   30ms

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

✉️ SPF#

PolicyRecord (teaterbloom.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-11 12:29:20
www185.21.41.231 (AS48854) (address records, no CNAME)
www vs bare domainSame network
teaterbloom.dk: 185.21.41.231 (AS48854)
www.teaterbloom.dk: 185.21.41.231 (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#

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

🏷️ SOA#

0ms
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-13 04:35:55
FieldValue
RegistrarPunktum dk A/S (direct)
Registered2020-11-25
Expires2026-11-30 (44d)

🔗 Same registrant#

25 domains
📋 WHOIS#

⏱️ Lookup Timing#

NS
34ms
A
30ms
MX
30ms
AAAA
26ms
TXT
120ms
CAA
36ms
HTTPS
26ms
TLSA
53ms
SOA
0ms
MTA-STS
44ms
DNSSEC
55ms
SRV
43ms
Total
342ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-09-29 23:22:52 shown 342ms 2 NS 1 A 2 MX 🔒 Secure
2026-09-26 11:39:08 478ms 2 NS 1 A 2 MX 🔒 Secure
2026-06-18 10:56:28 710ms 2 NS 1 A 2 MX 🔒 Secure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone