SurfaceMap › n › newsletter2go.de

newsletter2go.de

Checked 2026-10-21 23:31 UTC · first added 2026-10-21
✗Problems found Score 62 of 100

Domain & DNS

warn

20 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: josh.ns.cloudflare.com: "2026.10.2"; mary.ns.cloudflare.com: "2026.10.2". 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 newsletter2go.de ›

Mail

fail

15 passed 4 warn 2 failed

Areas

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

Problems

  • ✗
    No DMARC record
    DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5
  • ✗
    5 void lookups, over the limit of 2
    SPF · 5 include/redirect targets do not exist or have no records. More than 2 makes receivers reject the SPF record (permerror). Remove the stale includes.
    #26
  • !
    10 of 10 DNS lookups, with problems
    SPF · SPF record needs 10 DNS lookups (limit is 10). Problems found: include:_s0.newsletter2go.de does not exist or has no records; include:_s1.newsletter2go.de does not exist or has no records; include:_s2.newsletter2go.de does not exist or has no records; include:_s3.newsletter2go.de does not exist or has no records; include:_s4.newsletter2go.de does not exist or has no records.
    #2
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    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 newsletter2go.de ›