SurfaceMap › t › teamfortress.com

teamfortress.com

Checked 2026-10-22 10:55 UTC · first added 2026-10-21
✗Problems found Score 69 of 100

Domain & DNS

warn

24 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers iSOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: a1-164.akam.net, a11-67.akam.net, a26-65.akam.net, a8-66.akam.net, a9-67.akam.net; only in the zone: a1-194.akam.net, a2-64.akam.net, a22-67.akam.net, a7-66.akam.net, a9-66.akam.net. a1-164.akam.net, a1-194.akam.net, a11-67.akam.net, a2-64.akam.net, a22-67.akam.net, a24-64.akam.net, a26-65.akam.net, a7-66.akam.net, a8-66.akam.net, a9-66.akam.net, a9-67.akam.net report NS a1-194.akam.net a2-64.akam.net a22-67.akam.net a24-64.akam.net a7-66.akam.net a9-66.akam.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-164.akam.net: "41824.6"; a1-164.akam.net: "41824.11"; a1-194.akam.net: "41824.11"; a1-194.akam.net: "41824.5"; a11-67.akam.net: "41824.4"; a11-67.akam.net: "41824.7"; a2-64.akam.net: "48878.32"; a2-64.akam.net: "48878.26"; a22-67.akam.net: "48878.30"; a22-67.akam.net: "48878.31"; a24-64.akam.net: "48878.33"; a24-64.akam.net: "48878.30"; a26-65.akam.net: "48878.31"; a26-65.akam.net: "48878.33"; a7-66.akam.net: "41824.7"; a7-66.akam.net: "41824.10"; a8-66.akam.net: "48878.32"; a8-66.akam.net: "48878.27"; a9-66.akam.net: "41824.5"; a9-66.akam.net: "41824.6"; a9-67.akam.net: "41824.9"; a9-67.akam.net: "41824.5". 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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s). Low TTLs are useful just before a planned change.
    #32

Recent checks

!

Full report

Domain & DNS report for teamfortress.com ›

Mail

fail

23 passed 3 warn 1 failed

Areas

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

Problems

  • ✗
    No DKIM keys published
    DKIM · _domainkey.teamfortress.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com
    #11
  • !
    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 teamfortress.com ›