SurfaceMap › r › rollingstone.de

rollingstone.de

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

Domain & DNS

warn

26 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC iRecords

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-130.akam.net: "41824.8"; a1-130.akam.net: "41824.10"; a11-67.akam.net: "41824.8"; a11-67.akam.net: "41824.5"; a14-64.akam.net: "48878.27"; a14-64.akam.net: "48878.32"; a16-65.akam.net: "48878.29"; a16-65.akam.net: "48878.31"; a6-66.akam.net: "48878.33"; a7-67.akam.net: "41824.10"; a7-67.akam.net: "41824.11". Hide or replace the version string.
    #17
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 15 iterations and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

!

Full report

Domain & DNS report for rollingstone.de ›

Mail

fail

20 passed 6 warn 1 failed

Areas

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

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    4 of 10 DNS lookups, with problems
    SPF · SPF record needs 4 DNS lookups (limit is 10). Problems found: include:_spf.c136.freistilbox.net does not exist or has no records.
    #2
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    No aggregate reports (rua)
    DMARC · DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: mail (1024 bits), k1 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    1 void lookup
    SPF · 1 include/redirect target does not exist or has no records (limit is 2). This usually is a stale include; remove it.
    #26
  • !
    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

Recent checks

✗

Full report

Mail report for rollingstone.de ›