Skip to content
https://tampabay.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 324 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 324 B Sitemaps referenced 0 User-agents *, anthropic-ai, Bytespider, ClaudeBot, Aolbot-News, GPTbot, CCBot, OmigiliBot, Diffbot Blocking No — crawling allowed
# Robots.txt

User-agent: *
Allow: /ads.txt

User-agent: Aolbot-News 
Disallow: /

User-agent: GPTbot
Disallow: / 

User-agent: anthropic-ai
Disallow: / 

User-agent: CCBot
Disallow: /

User-agent: OmigiliBot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: ClaudeBot
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.tampabay.com/
200https://tampabay.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

85
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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
2 A records, 40 ms lookup
PASS
2 A records, 40 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 2.19.117.97, 2.19.117.91
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:5d00:6::6011:b385, 2a02:26f0:5d00:6::684f:5de3
Info::
2 nameserver(s) configured
Got: luke.ns.cloudflare.com, sandy.ns.cloudflare.com
Info::
1 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: 40 ms
Got: 40 ms
A2.19.117.97, 2.19.117.91
AAAA2a02:26f0:5d00:6::6011:b385, 2a02:26f0:5d00:6::684f:5de3
CNAME
NSluke.ns.cloudflare.com, sandy.ns.cloudflare.com
MX
0 tampabay-com.mail.protection.outlook.com
TXT
MS=ms23684061
cloudflare-verify.tampabay.com contains 953263986-59223538
SPF v=spf1 include:spf.protection.outlook.com include:amazonses.com include:_spf.goo...
tollbit-domain-verification=55ebe0715bf965d850976b52791b2eca25889bf45fdf0edd935a...
google-site-verification=lKx0Uqrh1G_A51fgHnn-93EOUFy_5DBBYUDZnj-Voe0
globalsign-domain-verification=C30AF64165F783A012AC0C7D01DEB5D0
CAALookup not available with standard resolver
Resolved in 40 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), 686 ms total
PASS
1 redirect(s), 686 ms total
Info::
Single redirect
Got: https://tampabay.com → https://www.tampabay.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 686 ms total
Got: 686 ms

https://tampabay.com

117 ms · HTTP/1.1

301

https://www.tampabay.com/

568 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tampabay.com301117 msHTTP/1.1AkamaiGHost
2https://www.tampabay.com/200568 msHTTP/1.1openresty

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:5d00:6::6011:b385, 2a02:26f0:5d00:6::684f:5de3
Got: 25 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:5d00:6::6011:b385, 2a02:26f0:5d00:6::684f:5de3 Connection Reachable (25 ms)
A
Domain Intelligence
tampabay.com — via GoDaddy.com, LLC, 31 years, 4 months old
PASS
tampabay.com — via GoDaddy.com, LLC, 31 years, 4 months old
Warning::
Domain expires in 40 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 1, 2026
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.
Domain expiry

EXPIRED

June 1, 2026

SSL certificate

85 days

Issued by Let's Encrypt

Domain age

31 years, 4 months

Registered June 2, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:5d00:6::6011:b385

Registrar

GoDaddy.com, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created June 2, 1995 (31 years, 4 months ago)
Expires June 1, 2026 (1 months)
Last Updated May 27, 2025
Name Servers luke.ns.cloudflare.com, sandy.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a02:26f0:5d00:6::6011:b385
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 43 ms TCP Connect 25 ms TLS Handshake 29 ms Server Processing 45 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