SurfaceMap › j › jo-so.de

jo-so.de

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

Domain & DNS

fail

24 passed 2 warn 1 failed

Areas

iRegistration iDelegation iNameservers ✓SOA ✗DNSSEC ✓Records

Problems

  • ✗
    Signatures expired
    DNSSEC · The DNSSEC signatures expired at 2026-10-20 09:50 UTC; validating resolvers reject the zone.
    #30
  • !
    Signed but not delegated securely
    DNSSEC · The zone is signed but the parent has no DS record, so the signatures are not used. Publish the DS record at your registrar.
    #27
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 0 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 jo-so.de ›

Mail

fail

15 passed 5 warn 4 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
  • ✗
    No DKIM keys published
    DKIM · _domainkey.jo-so.de does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • ✗
    Signatures expired
    DNSSEC · DNSKEY signatures expired at 2026-10-20T09:50:00Z. Validating resolvers will fail to resolve this domain.
    #21
  • ✗
    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: jo-so.de.
    #36
  • !
    Signed, but no DS at parent
    DNSSEC · The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #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
  • !
    Reverse DNS does not match
    MX · The PTR name of these addresses does not resolve back to the same address: 2a03:4000:8:213::1 -> ptr.0001.0000.0000.0000.0213.0008.4000.2a03.static.yourvserver.net.
    #30
  • !
    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 jo-so.de ›