SurfaceMap › v › vsa-verlag.de

vsa-verlag.de

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

Domain & DNS

fail

21 passed 2 warn 1 failed

Areas

iRegistration iDelegation !Nameservers ✗SOA !DNSSEC iRecords

Problems

  • ✗
    Invalid contact address
    SOA · The SOA RNAME "hostmaster\\@syncope.de" contains an @; it must be written with a dot instead (hostmaster.example.com).
    #25
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.syncope.de: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)"; ns2.syncope.de: "PowerDNS Authoritative Server 5.0.7 (built Aug 6 2026 00:00:00 by mockbuild@localhost)". Hide or replace the version string.
    #17
  • !
    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 vsa-verlag.de ›

Mail

fail

17 passed 5 warn 2 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.vsa-verlag.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: matangi.syncope.it
    #11
  • !
    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
  • !
    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 vsa-verlag.de ›