SurfaceMap › t › tician.de

tician.de

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

Domain & DNS

fail

18 passed 4 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Zone transfer allowed
    Nameservers · These nameservers send the complete zone to anyone who asks (AXFR), exposing all host names: ns1.tiker.net (49.13.195.233): 16 records; ns1.tiker.net (2a01:4f8:1c1b:7294::1): 16 records. Restrict zone transfers to your secondary servers.
    #18
  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: ns2.tiker.net; only in the zone: ns2.he.net, ns3.he.net, ns4.he.net, ns5.he.net. ns1.tiker.net, ns2.he.net, ns2.tiker.net, ns3.he.net, ns4.he.net, ns5.he.net report NS ns1.tiker.net ns2.he.net ns3.he.net ns4.he.net ns5.he.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.tiker.net: "9.20.29-1-Debian". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 1h.
    #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

Recent checks

✗

Full report

Domain & DNS report for tician.de ›

Mail

warn

25 passed 4 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #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
  • !
    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:inform+dmarc@tiker.net (needs tician.de._report._dmarc.tiker.net). Ask the report provider to publish the record, or check the address.
    #29
  • !
    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 tician.de ›