Skip to content
https://ti.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.ti.com/
200https://ti.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ti.com/ → http://www.ti.com/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
TLS Certificate Expiry & Recommendations
159 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

159
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 140 ms lookup
PASS
1 A records, 140 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.47.23.159
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
9 nameserver(s) configured
Got: ns3.ti.com, ns-b.pnap.net, ns2.ti.com, ns4.ti.com, ns-c.pnap.net, ns-d.pnap.net, ns.ti.com, nsde.ti.com, ns-a.pnap.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 140 ms
Got: 140 ms
A198.47.23.159
AAAA—
CNAME—
NSns3.ti.com, ns-b.pnap.net, ns2.ti.com, ns4.ti.com, ns-c.pnap.net, ns-d.pnap.net, ns.ti.com, nsde.ti.com, ns-a.pnap.net
MX
10 mxb-0002e601.gslb.pphosted.com
10 mxa-0002e601.gslb.pphosted.com
TXT
webexdomainverification.=1bac9ab1-5ad9-4845-941c-0b24a8601144
apple-domain-verification=7tJkLNXRI9Z0OVDp
docusign=dd445e38-75bd-4999-8bb4-9475837a6acd
webexdomainverification.=c1bca203-ac7d-44a9-afd8-a5d9a13c16e1
google-site-verification=1feRQdV5e-V6-VOKGRqUgaAEluhx4TKQ4ScUFfuXfuY
webexdomainverification.=d90aaa66-5919-4a7d-8671-d005f04687c0
autodesk-domain-verification=pqNgbQhuvDfwbmKT3omV
docusign=943799bd-c6d5-464f-9fdc-7113e761b5e2
webexdomainverification.=0033192c-1840-4ca0-9ee0-637c115a0c89
canva-site-verification=lqkcrgm6zN2hKP46tRzi_w
canva-site-verification=AbwcAdo3ie9ch6qYT3zg1g
webexdomainverification.GID5=eeea08ab-4ccd-475e-ba7a-69c38cf60701
SPF v=spf1 include:spf.ti.com ip4:52.5.134.202 include:sendgrid.net include:service-...
remarkable-domain-verification=d614b48d-fb8d-41f3-973a-9e68b266a930
MFC=2b819a7d-a326-4386-8edb-b47226f08331
ciscocidomainverification=31bc2cfc630297c963d60870e3c0db2d117ce271ff92733118636e...
autodesk-domain-verification=LjM1fAWH7TrNIhunt05V
CAALookup not available with standard resolver
Resolved in 140 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 446 ms total
PASS
1 redirect(s), 446 ms total
Info::
Single redirect
Got: https://ti.com → https://www.ti.com/ (301)
Info::
WWW normalization redirect

https://ti.com

392 ms · HTTP/1.1

301

https://www.ti.com/

55 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ti.com301392 msHTTP/1.1Apache
2https://www.ti.com/20055 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 52 URLs
PASS
robots.txt present, sitemap with 52 URLs
Info::
robots.txt is present
Got: 1284 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 52 entries
Info::
Sitemap index with 52 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1284 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Crawl-delay: 1
Disallow: /bin/ti/
Disallow: /general/docs/userdeviceincart.tsp
Disallow: /webemail/
Disallow: /myti/docs/
Disallow: /myti/nsdocs/
Disallow: /sitesearch/docs/xrefdirectedsearch.tsp
Disallow: /sitesearch/cn/docs/xrefdirectedsearch.tsp
Disallow: /sitesearch/jp/docs/xrefdirectedsearch.tsp
Disallow: /sitesearch/docs/partnumsearch.tsp
Disallow: /sitesearch/cn/docs/partnumsearch.tsp
Disallow: /sitesearch/jp/docs/partnumsearch.tsp
Disallow: /about-ti/careers-maintenance.html
Disallow: /sitesearch/docs/universalsearch.tsp
Disallow: /sitesearch/docs/cn/universalsearch.tsp
Disallow: /sitesearch/docs/jp/universalsearch.tsp
Disallow: /sitesearch/docs/de/universalsearch.tsp
Disallow: /sitesearch/docs/kr/universalsearch.tsp
Disallow: /materialcontent/en/search
Disallow: /materialcontent/cn/search
Disallow: /materialcontent/jp/search
Disallow: /materialcontent/de/search
Disallow: /materialcontent/kr/search
Disallow: /general/en/docs/refdesignsearchresults.tsp
Disallow: /general/cn/docs/refdesignsearchresults.tsp
Disallow: /general/jp/docs/refdesignsearchresults.tsp
Disallow: /general/de/docs/refdesignsearchresults.tsp
Disallow: /general/kr/docs/refdesignsearchresults.tsp
Disallow: /productmodel/
Sitemap: https://www.ti.com/sitemapindex-standard.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 52 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ti.com — via GoDaddy.com, LLC, 40 years, 7 months old, hosted on TI-AS - Texas Instruments Incorporated, US
PASS
ti.com — via GoDaddy.com, LLC, 40 years, 7 months old, hosted on TI-AS - Texas Instruments Incorporated, US
Info::
Domain registered until May 31, 2027 (1 years, 1 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: GoDaddy.com, LLC
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: TI-AS - Texas Instruments Incorporated, US
Got: AS161
Domain expiry

350 days

May 31, 2027

SSL certificate

159 days

Issued by DigiCert Inc

Domain age

40 years, 7 months

Registered March 25, 1986

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

TI-AS - Texas Instruments Incorporated, US

ASN AS161

198.47.23.159

Registrar

GoDaddy.com, LLC

Unlocked 9 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created March 25, 1986 (40 years, 7 months ago)
Expires May 31, 2027 (1 years, 1 months)
Last Updated January 28, 2026
Name Servers ns-a.pnap.net, ns-b.pnap.net, ns-c.pnap.net, ns-d.pnap.net, ns.ti.com, ns2.ti.com, ns3.ti.com, ns4.ti.com, nsde.ti.com
DNSSEC Not enabled
Hosting
IP Address 198.47.23.159
ASN AS161 (TI-AS - Texas Instruments Incorporated, US)
Provider TI-AS - Texas Instruments Incorporated, US
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 427 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
34 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
128 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
134 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
428 ms
Total Time Total request time from DNS lookup through full response.
428 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 128 ms TLS Handshake 134 ms Server Processing 131 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback