Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from Madrid, Spain

403 Forbidden

Checks

7 PASS 10 REVIEW

DNS Records

2 A records, 1039 ms lookup

REVIEW

2 A records, 1039 ms lookup

Resolves to 2 IPv4 address(es)

Got: 104.16.79.180, 104.16.64.211

Has 2 IPv6 (AAAA) record(s)

Got: 2606:4700::6810:40d3, 2606:4700::6810:4fb4

No NS records found

No MX records — email not configured via DNS

No SPF record found in TXT records

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

DNS resolution is slow (1039 ms)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Got: 1039 ms

A	104.16.79.180, 104.16.64.211
AAAA	2606:4700::6810:40d3, 2606:4700::6810:4fb4
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 1039 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

DNSSEC

Unsigned (DNSSEC not deployed)

REVIEW

Unsigned (DNSSEC not deployed)

DNSSEC is not deployed

The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).

CAA Records

No CAA records (any CA may issue certificates)

REVIEW

No CAA records (any CA may issue certificates)

No CAA records published

Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.

Reverse DNS

Action

0/4 IPs match cert SAN

REVIEW

0/4 IPs match cert SAN

PTR lookup failed for 104.16.79.180: lookup 104.16.79.180: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 104.16.64.211: lookup 104.16.64.211: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700::6810:40d3: lookup 2606:4700::6810:40d3: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

PTR lookup failed for 2606:4700::6810:4fb4: lookup 2606:4700::6810:4fb4: no such host

No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.

Multi-Resolver DNS Speed

Action

Mean 111ms across 3 resolvers (spread 252ms)

REVIEW

Mean 111ms across 3 resolvers (spread 252ms)

Cloudflare: 27ms

Got: 27ms via 1.1.1.1:53

Google: 27ms

Got: 27ms via 8.8.8.8:53

Quad9: 279ms

Got: 279ms via 9.9.9.9:53

High latency spread between resolvers: 252ms (min 27ms / max 279ms)

Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.

Crawlability

no robots.txt, no sitemap

REVIEW

no robots.txt, no sitemap

No robots.txt found

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

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.

TLS Certificate Expiry & Recommendations

42 days until leaf cert expires — 4 issues to address

REVIEW

Certificate validity

days left

0d 30d 60d 90d+

Recommended actions

Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
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

CDN & Delivery

Cloudflare

REVIEW

Cloudflare

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a544c4bf6a01f45b-CDG

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a544c4bf6a01f45b-CDG

CDN Cache Observability

No CDN cache-status headers in the response

REVIEW

No CDN cache-status headers in the response

Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.

Operational Status Page

No status page link detected

REVIEW

No status page link detected

No operational status page link detected

Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Redirect Chain

0 redirect(s), 86 ms total

PASS

0 redirect(s), 86 ms total

https://www.planetfitness.mx

86 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.planetfitness.mx	403	86 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (17 ms)

PASS

IPv6 reachable (17 ms)

IPv6 is configured and reachable at 2606:4700::6810:40d3, 2606:4700::6810:4fb4

Got: 17 ms connect

IPv6 Ready

AAAA Records 2606:4700::6810:40d3, 2606:4700::6810:4fb4 Connection Reachable (17 ms)

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.planetfitness.mx/

403https://planetfitness.mx/

HTTP → HTTPS

301http://www.planetfitness.mx/ → https://www.planetfitness.mx/

Consistent

A+

Domain Intelligence

planetfitness.mx — via GoDaddy Corporate Domains, LLC, 16 years, 2 months old

PASS

planetfitness.mx — via GoDaddy Corporate Domains, LLC, 16 years, 2 months old

Domain registered until Nov 9, 2027 (1 years remaining)

Registrar: GoDaddy Corporate Domains, LLC

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

365 days

November 9, 2027

SSL certificate

42 days

Issued by Google Trust Services

Domain age

16 years, 2 months

Registered November 10, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6810:40d3

Registrar

GoDaddy Corporate Domains, LLC

Unlocked 2 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar GoDaddy Corporate Domains, LLC

Created November 10, 2010 (16 years, 2 months ago)

Expires November 9, 2027 (1 years)

Last Updated October 10, 2026

Name Servers dane.ns.cloudflare.com, hope.ns.cloudflare.com

Hosting

IP Address 2606:4700::6810:40d3

Data source: whois (0.9s)

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 117 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

38 ms

TCP Connect

17 ms

TLS Handshake

31 ms

Time to First Byte

117 ms

Total Time

117 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 31 ms Server Processing 32 ms Content Transfer 0 ms

A+

Health Check Endpoint

Auth-protected health endpoint at https://www.planetfitness.mx/health (HTTP 403)

PASS

Auth-protected health endpoint at https://www.planetfitness.mx/health (HTTP 403)

Auth-protected health endpoint exposed at https://www.planetfitness.mx/health

Got: https://www.planetfitness.mx/health

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.