studiomitte.dk

Records from scan: 2026-10-02 14:05:58  ·  704ms total  ·  last checked 2026-10-20 13:44 (unchanged)
⬇ Zone File 📜 Timeline & History ⚡ Scan Now

studiomitte.dk is a .dk domain served by 3 nameservers (ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de). It was already in the .dk zone when our tracking began on 16 June 2026. Its website address 78.47.47.20 is hosted by Hetzner Online GmbH (AS24940) in Germany. Mail is handled by aspmx.l.google.com, mail.studiomitte.dk and 4 more. The zone is not DNSSEC-signed, 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#

3 records   48ms

🌍 A Records#

1 records   50ms

📧 MX Records#

6 records   39ms

📧 Autodiscover / Autoconfig#

ServiceCNAME / IP
🔶 Autoconfigmail.your-server.de → 78.46.5.205

🔷 AAAA Records (IPv6)#

✗ No AAAA records — IPv6 not configured

🔐 HTTPS Records#

✗ No HTTPS RR — no SVCB/HTTPS service binding

🔌 SRV Records#

1 records   114ms
ServicePriorityWeightPortTarget
_autodiscover._tcp 0 100 443 mail.your-server.de

📝 TXT Records#

2 records   272ms
TXT Record
v=spf1 +a +mx ?all
v=spf1 a mx include:_spf.google.com ~all

✉️ SPF#

⚠ Multiple SPF records — RFC 7208 §4.5 violation (receivers must treat this as permerror)
PolicyRecord (studiomitte.dk)
?all (neutral) v=spf1 +a +mx ?all
~all (soft fail) v=spf1 a mx include:_spf.google.com ~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-07 16:27:24
www78.47.47.20 (AS24940) (address records, no CNAME)
www vs bare domainSame network
studiomitte.dk: 78.47.47.20 (AS24940)
www.studiomitte.dk: 78.47.47.20 (AS24940)
WildcardNo

🔎 SPF check#

zone-wide SPF report

DNS lookups: 2/10 · policy: ?all

  • error 2 SPF records: receivers must treat that as a permanent error (RFC 7208 §4.5)
  • 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#

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

🏷️ SOA#

59ms
FieldValue
Serial2026010800
Primary NS (MNAME)ns1.your-server.de
Responsible (RNAME)postmaster@your-server.de
Refresh86400s
Retry10800s
Expire3600000s
Minimum (neg-cache TTL)7200s

📋 Registration#

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

⏱️ Lookup Timing#

NS
48ms
A
50ms
MX
39ms
AAAA
46ms
TXT
272ms
CAA
48ms
HTTPS
65ms
TLSA
104ms
SOA
59ms
MTA-STS
99ms
DNSSEC
96ms
SRV
114ms
Total
704ms

🕐 Scan History#

Scanned AtDurationRecordsDNSSEC
2026-10-02 14:05:58 shown 704ms 3 NS 1 A 6 MX 🔓 Insecure
2026-10-01 00:32:09 1080ms 3 NS 1 A 6 MX 🔓 Insecure
2026-09-25 20:51:28 9790ms 3 NS 1 A 6 MX 🔓 Insecure
2026-08-27 10:31:50 1790ms 3 NS 1 A 6 MX 🔓 Insecure
2026-06-29 23:17:26 1076ms 3 NS 1 A 6 MX 🔓 Insecure
2026-06-25 03:26:16 1107ms 3 NS 1 A 6 MX 🔓 Insecure
2026-06-20 07:08:39 1156ms 3 NS 1 A 6 MX 🔓 Insecure
2026-06-18 05:39:35 1109ms 3 NS 1 A 6 MX 🔓 Insecure
dhd.dk [/] search Domains, Hosts & DNS — .dk zone