Skip to content
https://tmz.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
4 PASS 4 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
Redirect Chain
1 redirect(s), 1003 ms total
REVIEW
1 redirect(s), 1003 ms total
Info::
Single redirect
Got: https://tmz.com → https://www.tmz.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1003 ms total
Got: 1003 ms

https://tmz.com

534 ms · HTTP/1.1

301

https://www.tmz.com/

469 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tmz.com301534 msHTTP/1.1urllo
2https://www.tmz.com/200469 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

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
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.tmz.com/
200https://tmz.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://tmz.com/ → https://tmz.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
A+
DNS Records
2 A records, 115 ms lookup
PASS
2 A records, 115 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.248.160.137, 76.223.34.124
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1388.awsdns-45.org, ns-1748.awsdns-26.co.uk, ns-385.awsdns-48.com, ns-552.awsdns-05.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: 115 ms
Got: 115 ms
A13.248.160.137, 76.223.34.124
AAAA—
CNAME—
NSns-1388.awsdns-45.org, ns-1748.awsdns-26.co.uk, ns-385.awsdns-48.com, ns-552.awsdns-05.net
MX
10 mxa-00195501.gslb.pphosted.com
10 mxb-00195501.gslb.pphosted.com
TXT
DZC=2Tzrc9Y
MS=ms20293001
MS=ms92300788
ZOOM_verify_DZ0OJw5nIxx8YBSAzNZoei
_globalsign-domain-verification=saFKi2eoh0C2_2LqU6CaQMHU9k54Zy2jRkAWlQemch
adobe-idp-site-verification=16507177c1c9529c1afbe70d5366baa0de29017e1eff100a4c3a...
adobe-sign-verification=c005311c2af6d5899b1dd7bb7415d17
airtable-verification=2ad0b6c3b5e5222653e94ed5623f69a5
apple-domain-verification=zVGibnrn75Vx5U2n
atlassian-domain-verification=S1WmZ0DNA7/gfhdmncHWSoiwNi92v5ZbRVj2ykMutlYyyxynFh...
facebook-domain-verification=inyndlryg5l9yuaf1estkjebndv9aj
google-gws-recovery-domain-verification=44662153
google-site-verification=M3gBTxgmDADGYISbfmmH0iS5as7k2oqEq5Mz_RU2pqE
google-site-verification=fjxBM59zskthuFL3pNfH6WgMkv-4pKZnj13Hv_NgQxg
google-site-verification=oMaX6GcLpev9twJIsNmBjaX3TI6IA1gj7ExrMETMQno
logmein-verification-code=pqSl0sEqV0Vy6M47LVSjdZ7CL
lucid-verification=bu7y@90V8fUHRs%c
openai-domain-verification=dv-fun0CzJBzflPqf9eBpWjSNkm
SPF v=spf1 include:spf.protection.outlook.com include:spf-00195501.pphosted.com ~all
wiz-domain-verification=c3c764bf81694baace883b328d4873e9e45ec9ed342c0a281ec509fe...
yDjTZMsl4pPfjhyGsqkEMlPUQDJ7elMC/kQU5gKMALoV+tJOqYcVABMYwWvW/4MS6XRVviTvE/CuvyB5...
CAALookup not available with standard resolver
Resolved in 115 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+
Crawlability
robots.txt present, sitemap with 248 URLs
PASS
robots.txt present, sitemap with 248 URLs
Info::
robots.txt is present
Got: 592 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 248 entries
Info::
Sitemap index with 248 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 592 B Sitemaps referenced 7 User-agents proximic, bingbot, *, Googlebot-News Blocking No — crawling allowed
Sitemap: https://www.tmz.com/sitemaps/article/index.xml
Sitemap: https://www.tmz.com/sitemaps/category/index.xml
Sitemap: https://www.tmz.com/sitemaps/gallery/index.xml
Sitemap: https://www.tmz.com/sitemaps/page/index.xml
Sitemap: https://www.tmz.com/sitemaps/person/index.xml
Sitemap: https://www.tmz.com/sitemaps/watch/index.xml
Sitemap: https://www.tmz.com/sitemaps/news.xml

User-agent: Googlebot-News
Disallow: /photos
Disallow: /watch

User-agent: proximic
Disallow:

User-agent: bingbot
Crawl-delay: 60

User-agent: *

Disallow: /_/
Disallow: */print
Disallow: /search
Disallow: /xid
sitemap.xml 200 OK
Type Sitemap Index URLs 248 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
tmz.com — via GoDaddy Corporate Domains, LLC, 30 years, 7 months old, hosted on AWS
PASS
tmz.com — via GoDaddy Corporate Domains, LLC, 30 years, 7 months old, hosted on AWS
Info::
Domain registered until Feb 16, 2031 (4 years, 10 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 Corporate Domains, 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: AWS
Got: AS16509
Domain expiry

1676 days

February 16, 2031

SSL certificate

85 days

Issued by Let's Encrypt

Domain age

30 years, 7 months

Registered February 15, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

13.248.160.137

Registrar

GoDaddy Corporate Domains, LLC

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 GoDaddy Corporate Domains, LLC
Created February 15, 1996 (30 years, 7 months ago)
Expires February 16, 2031 (4 years, 10 months)
Last Updated September 20, 2022
Name Servers ns-1388.awsdns-45.org, ns-1748.awsdns-26.co.uk, ns-385.awsdns-48.com, ns-552.awsdns-05.net
DNSSEC Not enabled
Hosting
IP Address 13.248.160.137
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.7s)

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 566 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.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
348 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
566 ms
Total Time Total request time from DNS lookup through full response.
567 ms

Connection waterfall

DNS Lookup 43 ms TCP Connect 1 ms TLS Handshake 348 ms Server Processing 174 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