SurfaceMap › v › videobuster.de

videobuster.de

Checked 2026-10-22 00:51 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

24 passed 3 warn 0 failed

Areas

iRegistration !Delegation ✓Nameservers !SOA !DNSSEC ✓Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.he.net, ns5.he.net. ns1.first-ns.de, ns1.he.net, ns2.he.net, ns3.he.net, ns4.he.net, ns5.he.net, robotns2.second-ns.de, robotns3.second-ns.com report NS ns1.first-ns.de ns1.he.net ns2.he.net ns3.he.net ns4.he.net ns5.he.net robotns2.second-ns.de robotns3.second-ns.com.
    #7
  • !
    Unusual SOA timers
    SOA · refresh 4m is outside 20m–1d; negative caching TTL (minimum) 2m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 4m, retry 30s, expire 1000h, negative TTL 2m.
    #23
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

!

Full report

Domain & DNS report for videobuster.de ›

Mail

fail

25 passed 5 warn 1 failed

Areas

✓SPF ✓DMARC !DKIM !DNSSEC !MX ✗TLS iBIMI

Problems

  • ✗
    TLSA records not DNSSEC-validated
    TLS · These MX hosts publish TLSA records that the resolver could not validate with DNSSEC, so senders ignore them or, if validation fails, may refuse delivery: mx1179.videobuster.de.
    #36
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32
  • !
    Not configured
    TLS · MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35

Recent checks

✗

Full report

Mail report for videobuster.de ›