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 Santa Clara, United States

403 Forbidden

Checks

8 PASS 9 REVIEW

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

0/1 IPs match cert SAN

REVIEW

0/1 IPs match cert SAN

PTR for 23.227.38.65 does not match any cert SAN: myshopify.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.

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

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

46 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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

CDN & Delivery

Document on Cloudflare; assets also on Fastly, Bunny CDN

REVIEW

Document on Cloudflare; assets also on Fastly, Bunny CDN

Document is served via Cloudflare CDN (edge: SJC)

Got: cf-ray: a4eb61daca1a9cd0-SJC

Assets on Cloudflare: cdn.shopify.com (assets: 56), cache HIT

Got: cf-ray: a4eb64db9f0e15e3-SJC

Assets on Fastly: static.klaviyo.com (assets: 11), cache DYNAMIC

Got: delegation klaviyo-onsite.map.fastly.net

Assets on Bunny CDN: public-images.judge.me (assets: 6)

Got: delegation public-images.b-cdn.net

Assets on Bunny CDN: review-images.judgeme.com (assets: 5)

Got: delegation review-images.b-cdn.net

Assets on Fastly: static-tracking.klaviyo.com (assets: 4), cache HIT, HIT

Got: delegation klaviyo-app.map.fastly.net

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a4eb61daca1a9cd0-SJC

Asset hosts on a CDN

cdn.shopify.com — Cloudflare · assets: 56 · Cache Status: HIT
static.klaviyo.com — Fastly · assets: 11 · Cache Status: DYNAMIC
public-images.judge.me — Bunny CDN · assets: 6
review-images.judgeme.com — Bunny CDN · assets: 5
static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT

Other asset hosts

connect.facebook.net — assets: 2 · below probe threshold
js.smile.io — assets: 2 · below probe threshold
www.googletagmanager.com — assets: 2 · below probe threshold
assets.tapcart.com — assets: 1 · below probe threshold
cdn.klaviyomail.com — assets: 1 · below probe threshold
qrcode.tapcart.com — assets: 1 · below probe threshold
shop.app — assets: 1 · below probe threshold
storage.googleapis.com — assets: 1 · below probe threshold
unpkg.com — assets: 1 · below probe threshold

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+

DNS Records

1 A records, 17 ms lookup

PASS

1 A records, 17 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.227.38.65

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

2 nameserver(s) configured

Got: ns55.domaincontrol.com, ns56.domaincontrol.com

5 mail exchanger(s) configured

SPF record present in TXT

DNS resolution time: 17 ms

Got: 17 ms

A	23.227.38.65
AAAA	—
CNAME	—
NS	ns55.domaincontrol.com, ns56.domaincontrol.com
MX	1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com
TXT	google-site-verification=gkfyE6s6Ydtg9SSkDAAhMdheZ6VCPY1dx4BdqfuFuh4 klaviyo-site-verification=KmVV2y apple-domain-verification=AGQkHRtBapRpH3J7 pinterest-site-verification=01bd18145ac97cc3b0edca4c379acf7a google-site-verification=A5tlOjOpYcqkhGj-FXXTh8Eb-lGqQDOjSWuNkQpCL_0 SPF v=spf1 include:_spf.google.com include:shops.myshopify.com include:gorgias.com ~... google-site-verification=lAtbiXGe6pkBkXyXIFS-nWwKi_Z4XDzEcH2wiC_2z7E
CAA	Lookup not available with standard resolver

Resolved in 17 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 7ms across 3 resolvers (spread 6ms)

PASS

Mean 7ms across 3 resolvers (spread 6ms)

Cloudflare: 4ms

Got: 4ms via 1.1.1.1:53

Quad9: 9ms

Got: 9ms via 9.9.9.9:53

Google: 10ms

Got: 10ms via 8.8.8.8:53

A+

Redirect Chain

0 redirect(s), 42 ms total

PASS

0 redirect(s), 42 ms total

https://farmgirlsfancyfrills.com

42 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://farmgirlsfancyfrills.com	403	42 ms	HTTP/1.1	cloudflare

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

403https://www.farmgirlsfancyfrills.com/

200https://farmgirlsfancyfrills.com/

HTTP → HTTPS

301http://farmgirlsfancyfrills.com/ → https://farmgirlsfancyfrills.com/

Consistent

A+

Domain Intelligence

farmgirlsfancyfrills.com — via GoDaddy.com, LLC, 12 years, 7 months old, hosted on Cloudflare

PASS

farmgirlsfancyfrills.com — via GoDaddy.com, LLC, 12 years, 7 months old, hosted on Cloudflare

Domain registered until May 20, 2027 (6 months remaining)

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.

Registrar: GoDaddy.com, 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.

Hosting: Cloudflare

Got: AS13335

Domain expiry

209 days

May 20, 2027

SSL certificate

46 days

Issued by Let's Encrypt

Domain age

12 years, 7 months

Registered May 20, 2014

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

23.227.38.65

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC

Created May 20, 2014 (12 years, 7 months ago)

Expires May 20, 2027 (6 months)

Last Updated May 18, 2026

Name Servers ns55.domaincontrol.com, ns56.domaincontrol.com

DNSSEC Not enabled

Hosting

IP Address 23.227.38.65

ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)

Provider Cloudflare

Data source: rdap (0.1s)

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

PASS

DNS Lookup

19 ms

TCP Connect

3 ms

TLS Handshake

12 ms

Time to First Byte

42 ms

Total Time

42 ms

Connection waterfall

DNS Lookup 19 ms TCP Connect 3 ms TLS Handshake 12 ms Server Processing 9 ms Content Transfer 0 ms

A+

Health Check Endpoint

Health endpoint at https://farmgirlsfancyfrills.com/healthz (HTTP 200)

PASS

Health endpoint at https://farmgirlsfancyfrills.com/healthz (HTTP 200)

Public health endpoint at https://farmgirlsfancyfrills.com/healthz

Got: https://farmgirlsfancyfrills.com/healthz

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