SurfaceMap › a › adticket.de

adticket.de

Checked 2026-10-21 21:28 UTC · first added 2026-10-21
✗Problems found Score 68 of 100

Domain & DNS

warn

22 passed 2 warn 0 failed

Areas

iRegistration iDelegation ✓Nameservers ✓SOA !DNSSEC !Records

Problems

  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m), AAAA (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for adticket.de ›

Mail

fail

23 passed 2 warn 2 failed

Areas

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

Problems

  • ✗
    11 DNS lookups, over the limit of 10
    SPF · SPF record needs 11 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✗
    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
  • !
    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 adticket.de ›