Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 632 ms totalREVIEW
https://plex.tv
316 ms · HTTP/1.1
https://www.plex.tv/
137 ms · HTTP/1.1
https://watch.plex.tv/
179 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://plex.tv | 302 | 316 ms | HTTP/1.1 | |
| 2 | https://www.plex.tv/ | 301 | 137 ms | HTTP/1.1 | cloudflare |
| 3 | https://watch.plex.tv/ | 200 | 179 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BTLS Certificate Expiry & Recommendations154 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records3 A records, 40 ms lookupPASS
| A | 44.210.41.33, 34.238.225.186, 35.172.142.61 |
| AAAA | — |
| CNAME | — |
| NS | rafe.ns.cloudflare.com, jeremy.ns.cloudflare.com |
| MX | 0 alt1.aspmx.l.google.com 0 aspmx3.googlemail.com 0 aspmx.l.google.com 0 aspmx2.googlemail.com 0 alt2.aspmx.l.google.com |
| TXT | status-page-domain-verification=2dyn4v7qgzdb SPF v=spf1 include:sendgrid.net include:spf.messagingengine.com include:email2.plex.... _n842f05f02c08zlp8y4edng4c0b7oae google-site-verification=vD2hudbZhdcLlL2Chv-omogllPdGb6QSEKtT5oDQZzM google-site-verification=-kmee5sdIpB_wbPeOoCV3nFVV2T7uxEVsvjzVATk5yo google-site-verification=TIcKOSLgiuuRUScefdc_1q0a7M8HEj_plpWJTDABSjo google-site-verification=-p6MlJmsHz0SexGkQ3O-r7dzFZZvA82mPQG9vfDbgVs google-site-verification=FmSnzMbYmRm6mXvW0Tb4SCQyUuW2Vn5k7qgnbfEMbnc |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
A+Crawlabilityrobots.txt present, sitemap with 15 URLsPASS
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /servers
Disallow: /users
Disallow: /api
Disallow: /pms
Disallow: /admin
Disallow: /subscription
AURL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
A+Domain Intelligenceplex.tv — via Cloudflare, Inc., 17 years, 7 months old, hosted on AWSPASS
500 days
November 27, 2027
154 days
Issued by DigiCert Inc
17 years, 7 months
Registered November 27, 2008
Enabled
Protects against DNS spoofing
AWS
ASN AS16509
44.210.41.33
Cloudflare, Inc.
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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