Skip to content
https://fjackets.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
502 Bad Gateway
Checks
17
6 PASS 10 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 502 Expected: 301 redirect to HTTPS

www / non-www

200https://www.fjackets.com/
200https://fjackets.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

502http://fjackets.com/

HTTP version does not redirect to HTTPS

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
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).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
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.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 35.190.31.54 does not match any cert SAN: 54.31.190.35.bc.googleusercontent.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 34.160.81.203 does not match any cert SAN: 203.81.160.34.bc.googleusercontent.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 34.149.36.179 does not match any cert SAN: 179.36.149.34.bc.googleusercontent.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 35.244.153.44 does not match any cert SAN: 44.153.244.35.bc.googleusercontent.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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
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
184 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

184
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
C
CDN & Delivery
Action
Assets on Fastly (host static.klaviyo.com, 9 assets); document served directly from origin
REVIEW
Assets on Fastly (host static.klaviyo.com, 9 assets); document served directly from origin
Warning::
Document not behind existing CDN (Fastly serves the assets)
The page's subresources are delivered by Fastly (static.klaviyo.com, 9 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation klaviyo-onsite.map.fastly.net
Info::
Assets on Fastly: static.klaviyo.com (assets: 9), cache HIT, HIT
Got: delegation klaviyo-onsite.map.fastly.net
Info::
Assets on Fastly: static-tracking.klaviyo.com (assets: 4), cache HIT, HIT
Got: delegation klaviyo-app.map.fastly.net
Info::
Assets on Cloudflare: cdnjs.cloudflare.com (assets: 3), cache HIT
Got: cf-ray: a5872bd39bdd97b6-CDG
Warning: Assets on a CDN, document is not: Fastly
Document origin not attributed

Asset hosts on a CDN

  • static.klaviyo.com — Fastly · assets: 9 · Cache Status: HIT, HIT
  • static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT
  • cdnjs.cloudflare.com — Cloudflare · assets: 3 · Cache Status: HIT

Other asset hosts

  • www.fjackets.com — assets: 78 · not attributed
  • us-server.fjackets.com — assets: 3 · not attributed
  • connect.facebook.net — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • app.chatwoot.com — assets: 1 · below probe threshold
  • b-code.liadm.com — assets: 1 · below probe threshold
  • cdn.jsdelivr.net — assets: 1 · below probe threshold
  • s3-us-west-2.amazonaws.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
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.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A+
DNS Records
4 A records, 43 ms lookup
PASS
4 A records, 43 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 35.190.31.54, 34.160.81.203, 34.149.36.179, 35.244.153.44
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.siteground.net, ns2.siteground.net
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 43 ms
Got: 43 ms
A35.190.31.54, 34.160.81.203, 34.149.36.179, 35.244.153.44
AAAA—
CNAME—
NSns1.siteground.net, ns2.siteground.net
MX
10 mx10.antispam.mailspamprotection.com
20 mx20.antispam.mailspamprotection.com
30 mx30.antispam.mailspamprotection.com
TXT
_sitelock-domain-validation=14676ca5253b26a9
SPF v=spf1 +ip4:35.209.8.6 +a include:_spf.google.com +mx include:fjackets.com.spf.a...
google-site-verification=aygjaO6Rf6Okd192kacflThwYfTie3acACNZK2QvnWA
klaviyo-site-verification=HEVrZ4
CAALookup not available with standard resolver
Resolved in 43 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 37ms across 3 resolvers (spread 24ms)
PASS
Mean 37ms across 3 resolvers (spread 24ms)
Info::
Quad9: 24ms
Got: 24ms via 9.9.9.9:53
Info::
Google: 40ms
Got: 40ms via 8.8.8.8:53
Info::
Cloudflare: 48ms
Got: 48ms via 1.1.1.1:53
A+
Redirect Chain
0 redirect(s), 485 ms total
PASS
0 redirect(s), 485 ms total

https://fjackets.com

485 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fjackets.com502485 msHTTP/1.1nginx
A+
Domain Intelligence
fjackets.com — via Domain.com - Network Solutions, LLC, 13 years, 5 months old, hosted on Google Cloud
PASS
fjackets.com — via Domain.com - Network Solutions, LLC, 13 years, 5 months old, hosted on Google Cloud
Info::
Domain registered until Aug 19, 2028 (1 years, 9 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: Domain.com - Network Solutions, 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: Google Cloud
Got: AS396982
Domain expiry

646 days

August 19, 2028

SSL certificate

184 days

Issued by GlobalSign nv-sa

Domain age

13 years, 5 months

Registered August 19, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

34.149.36.179

Registrar

Domain.com - Network Solutions, LLC

Unlocked 2 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 Domain.com - Network Solutions, LLC
Created August 19, 2013 (13 years, 5 months ago)
Expires August 19, 2028 (1 years, 9 months)
Last Updated August 5, 2024
Name Servers ns1.siteground.net, ns2.siteground.net
DNSSEC Not enabled
Hosting
IP Address 34.149.36.179
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 45 ms TCP Connect 17 ms TLS Handshake 42 ms Server Processing 429 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