SurfaceMap › t › td00.de

td00.de

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

Domain & DNS

warn

21 passed 4 warn 0 failed

Areas

iRegistration iDelegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns0.xtm.es: "PowerDNS Authoritative Server 5.1.3 (built Jun 29 2026 17:44:24 by root@localhost)"; ns1.xtm.es: "PowerDNS Authoritative Server 5.1.3 (built Jun 29 2026 17:44:24 by root@localhost)"; ns2.xtm.es: "PowerDNS Authoritative Server 5.1.3 (built Jun 29 2026 17:44:24 by root@localhost)". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 14d, negative TTL 1m.
    #23
  • !
    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 (1s), AAAA (1s), MX (1s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for td00.de ›

Mail

fail

23 passed 7 warn 1 failed

Areas

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

Problems

  • ✗
    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: pain.td00.de.
    #36
  • !
    Policy: quarantine
    DMARC · DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts are CNAMEs
    MX · MX records must point to a host name with A/AAAA records, not to a CNAME: fallbackmx.thies.xyz -> proxy.tservic.es
    #22
  • !
    Report address not authorized
    DMARC · These report addresses are in another domain that has not agreed to receive your reports, so receivers will not send them: mailto:td00.de@dmarc.tservic.es (needs td00.de._report._dmarc.dmarc.tservic.es). Ask the report provider to publish the record, or check the address.
    #29
  • !
    Addresses without reverse DNS
    MX · These MX addresses have no PTR record, which many receivers treat as a spam signal: 2a01:4f9:c010:e75b::1 (no.pain.td00.de). Ask your hosting provider to set one.
    #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 td00.de ›