SurfaceMap › t › ti.com

ti.com

Checked 2026-10-22 11:04 UTC · first added 2026-10-21
✗Problems found Score 63 of 100

Domain & DNS

fail

24 passed 3 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

  • ✗
    Nameservers not responding
    Nameservers · These addresses did not answer, so resolvers waste time on timeouts: ns.ti.com (198.47.19.1): read udp 46.225.38.91:56171->198.47.19.1:53: i/o timeout; ns2.ti.com (198.47.19.2): read udp 46.225.38.91:33040->198.47.19.2:53: i/o timeout; ns3.ti.com (198.47.26.139): read udp 46.225.38.91:57370->198.47.26.139:53: i/o timeout; ns4.ti.com (198.47.26.138): read udp 46.225.38.91:36720->198.47.26.138:53: i/o timeout.
    #14
  • !
    No IPv6
    Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13
  • !
    Unusual SOA timers
    SOA · refresh 15m is outside 20m–1d; negative caching TTL (minimum) 1m is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 15m, retry 5m, expire 28d, 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

Recent checks

✗

Full report

Domain & DNS report for ti.com ›

Mail

warn

23 passed 6 warn 0 failed

Areas

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

Problems

  • !
    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 without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mxa-0002e601.gslb.pphosted.com, mxb-0002e601.gslb.pphosted.com
    #11
  • !
    Subdomains unprotected (sp=none)
    DMARC · DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector1 (1024 bits), selector2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    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 ti.com ›