Skip to content
https://thomasnet.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
94
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
6 PASS 2 REVIEW 1 FIX
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.

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

301
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
2 A records, 12 ms lookup
PASS
2 A records, 12 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 3.210.191.64, 54.165.195.247
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1f18:6743:fd05:567b:5ab5:e7fe:e63b, 2600:1f18:6743:fd07:c729:f887:6188:dc1c
Info::
4 nameserver(s) configured
Got: ns-1054.awsdns-03.org, ns-2002.awsdns-58.co.uk, ns-431.awsdns-53.com, ns-562.awsdns-06.net
Info::
5 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: 12 ms
Got: 12 ms
A3.210.191.64, 54.165.195.247
AAAA2600:1f18:6743:fd05:567b:5ab5:e7fe:e63b, 2600:1f18:6743:fd07:c729:f887:6188:dc1c
CNAME
NSns-1054.awsdns-03.org, ns-2002.awsdns-58.co.uk, ns-431.awsdns-53.com, ns-562.awsdns-06.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
TXT
5ed8d9a5-ec1a-46e1-abd2-cb94a84713c3
FA4DE98329
MS=D7D0158E0913C6CA31D2F378BBAE81239D5B8F83
ZOOM_verify_4T9VsSd4LvRUmeUoeMeYXP
adobe-idp-site-verification=4a74165fcd31ca395ec8aa3a3e829f17deb40842cfdc91430b90...
anthropic-domain-verification-mjrxm4=4PpxOYFyAEhXuBc2vrkzZfUqq
apple-domain-verification=5k44Qe3N3plhuG1r
apple-domain-verification=eKLGxNUShraBfwNFm5kYuVmgLm1o5-FXoFuYIbeKChc
asv=76b247887fcfb94ae6254e5b85af3809docusign=fbd44b44-ecc1-4d83-8ba6-b60bd8d705a...
atlassian-domain-verification=b681/gV3/O/kxtFBL5aHUpgIB6NptiDtnFrQih7+RvxVUch5x/...
bw=rHb70SvcimTZBeHClNUC1MaIweEgMeVGwDDwoQNjYoaT
cursor-domain-verification-j1v8h1=PeFmqHHHn06PLOQEJDeVgXdjh
datadome-domain-verify=lE2qRHhvYCK18IRzdLuIR4hc5NaQqcjW
e2ma-verification=1tl3
ge98qqq0fu3qeubfiuimhte5o6
google-site-verification=AG--266xINP1ERGkp2XKmDY6n1XbtZnO15cuYhJ5KU8
google-site-verification=ArEo5mts3xmjgGy5vnKMI1VnXzezEEo_BQF9NfKpG3M
google-site-verification=FW2b90jcUiDDzsau0759HMk9gBtGI6zdpXcspg6csN8
google-site-verification=NxtxZHlCdMYhB5otcDiCEgxxy24nCHw95hT49reyAks
google-site-verification=a2TIdz9tG2RzH0yDhjX3cSkCoxYrfmANHrrlNRRIeWE
google-site-verification=bDyvPrIj3jIMNindxwdUVIlI864MfqLl_zdYnhKpOC8
google-site-verification=dGG-JjeKXpakMSftd01mjBy7eAZILpvwBiQNAJc08B0
google-site-verification=f5L1KcHd0hQO0rfgiiYWGVhrvdvOd9eGLeujGtMxKrU
google-site-verification=uavpW_8E2OtFClzb4bKgAWsq75C0bkVnfYP1aQ_LGcY
google-site-verification=yHdYe0MYxWXlh5CHqUe_8X5zzrgUEcHPdXL_V9MwBEw
hubspot-developer-verification=MmEwYWVjYTctN2RiNC00YTI1LTliNWItNGZmM2FhNzJlYWY5
hubspot-developer-verification=Njk1ZWJmZDUtNjdmOC00NGNhLTg4ZjktZDgwNmVmY2JlNTI0
intacct-esk=87C8C91CB08F07EDE053AA06A8C0324C
jamf-site-verification=44-2DhnlZorntmq2zaMKNQ
knowbe4-site-verification=08714ef09117f0ffed7b965a3db80d87
linear-domain-verification=6hu45hff5dew
mongodb-site-verification=mtXm5yMCXDXBwmigsgwEyfzrpFlUYbAc
qo3cfs0r8vtmfhohtsgs5oujr0
remote-domain-verification=23d0c530-4928-43ba-9849-fbd635de8112
stripe-verification=7da4200a1fb2835887dfa55e4383c5c028021aff539f804529b30111191a...
stripe-verification=af5215fe7e98bfec54f1b8c97c4e4bfaf745ba9a902a86938543f79c26f6...
SPF v=spf1 include:_spf.salesforce.com include:amazonses.com include:242200.spf03.hu...
CAALookup not available with standard resolver
Resolved in 12 ms

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), 100 ms total
PASS
1 redirect(s), 100 ms total
Info::
Single redirect
Got: https://thomasnet.com → https://www.thomasnet.com/ (301)
Info::
WWW normalization redirect

https://thomasnet.com

44 ms · HTTP/1.1

301

https://www.thomasnet.com/

56 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://thomasnet.com30144 msHTTP/1.1awselb/2.0
2https://www.thomasnet.com/40356 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (7 ms)
PASS
IPv6 reachable (7 ms)
Info::
IPv6 is configured and reachable at 2600:1f18:6743:fd05:567b:5ab5:e7fe:e63b, 2600:1f18:6743:fd07:c729:f887:6188:dc1c
Got: 7 ms connect
IPv6 Ready
AAAA Records 2600:1f18:6743:fd05:567b:5ab5:e7fe:e63b, 2600:1f18:6743:fd07:c729:f887:6188:dc1c Connection Reachable (7 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.thomasnet.com/
200https://thomasnet.com/

HTTP → HTTPS

301http://thomasnet.com/ https://www.thomasnet.com/

Consistent

A+
Domain Intelligence
thomasnet.com — via Amazon Registrar, Inc., 29 years, 11 months old
PASS
thomasnet.com — via Amazon Registrar, Inc., 29 years, 11 months old
Info::
Domain registered until Oct 15, 2026 (5 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: Amazon Registrar, Inc.
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.
Domain expiry

93 days

October 15, 2026

SSL certificate

301 days

Issued by Amazon

Domain age

29 years, 11 months

Registered October 16, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:1f18:6743:fd07:c729:f887:6188:dc1c

Registrar

Amazon Registrar, Inc.

Unlocked 4 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 Amazon Registrar, Inc.
Created October 16, 1996 (29 years, 11 months ago)
Expires October 15, 2026 (5 months)
Last Updated September 10, 2025
Name Servers ns-1054.awsdns-03.org, ns-2002.awsdns-58.co.uk, ns-431.awsdns-53.com, ns-562.awsdns-06.net
DNSSEC Not enabled
Hosting
IP Address 2600:1f18:6743:fd07:c729:f887:6188:dc1c
Data source: rdap (0.0s)

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 49 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
49 ms
Total Time Total request time from DNS lookup through full response.
49 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 7 ms TLS Handshake 8 ms Server Processing 28 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