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

200 OK

Checks

10 PASS 7 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/2 IPs match cert SAN

REVIEW

0/2 IPs match cert SAN

PTR for 23.227.38.32 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.

PTR lookup failed for 2620:127:f00f:3::: lookup 2620:127:f00f:3::: 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.

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

70 days until leaf cert expires — 5 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 includeSubDomains to the HSTS directive
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

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.

Health Check Endpoint

No conventional health endpoint found

REVIEW

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: 404, /health: 429, /healthz: 429, /ping: 429, /status: 429.

DNS Records

1 A records, 34 ms lookup

PASS

1 A records, 34 ms lookup

Resolves to 1 IPv4 address(es)

Got: 23.227.38.32

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2620:127:f00f:3::

4 nameserver(s) configured

Got: ns-cloud-d2.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d4.googledomains.com, ns-cloud-d3.googledomains.com

1 mail exchanger(s) configured

No SPF record found in TXT records

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

DNS resolution time: 34 ms

Got: 34 ms

A	23.227.38.32
AAAA	2620:127:f00f:3::
CNAME	—
NS	ns-cloud-d2.googledomains.com, ns-cloud-d1.googledomains.com, ns-cloud-d4.googledomains.com, ns-cloud-d3.googledomains.com
MX	1 smtp.google.com
TXT	google-site-verification=2aYshJaJawcEiK6OrpQj8WBbWcJ4u90hSaMHmLQy7bY google-site-verification=V_cCqiYLRYW6kXFnT9REgDo1V70YKVZAtPl7U_vyfF0 klaviyo-site-verification=L8yrPY
CAA	Lookup not available with standard resolver

Resolved in 34 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

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)

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

No CNAME record present

A+

Multi-Resolver DNS Speed

Mean 21ms across 3 resolvers (spread 42ms)

PASS

Mean 21ms across 3 resolvers (spread 42ms)

Quad9: 1ms

Got: 1ms via 9.9.9.9:53

Google: 20ms

Got: 20ms via 8.8.8.8:53

Cloudflare: 43ms

Got: 43ms via 1.1.1.1:53

A+

Redirect Chain

0 redirect(s), 77 ms total

PASS

0 redirect(s), 77 ms total

https://forestinkclothing.com

77 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://forestinkclothing.com	429	77 ms	HTTP/1.1	cloudflare

A+

IPv6 Readiness

IPv6 reachable (16 ms)

PASS

IPv6 reachable (16 ms)

IPv6 is configured and reachable at 2620:127:f00f:3::

Got: 16 ms connect

IPv6 Ready

AAAA Records 2620:127:f00f:3:: Connection Reachable (16 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

429https://www.forestinkclothing.com/

200https://forestinkclothing.com/

HTTP → HTTPS

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

Consistent

Domain Intelligence

forestinkclothing.com — via Tucows Domains Inc., 3 years, 11 months old

PASS

forestinkclothing.com — via Tucows Domains Inc., 3 years, 11 months old

Domain expires in 31 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Nov 29, 2026

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: Tucows Domains Inc.

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

20 days

November 29, 2026

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

3 years, 11 months

Registered November 29, 2022

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:127:f00f:3::

Registrar

Tucows Domains Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Renew the domain or enable auto-renewal to prevent accidental expiry
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar Tucows Domains Inc.

Created November 29, 2022 (3 years, 11 months ago)

Expires November 29, 2026 (1 months)

Last Updated November 15, 2025

Name Servers ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com

DNSSEC Not enabled

Hosting

IP Address 2620:127:f00f:3::

Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

HTTP Probe Timing

Total 521 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

31 ms

TCP Connect

17 ms

TLS Handshake

27 ms

Time to First Byte

518 ms

Total Time

522 ms

Connection waterfall

DNS Lookup 31 ms TCP Connect 17 ms TLS Handshake 27 ms Server Processing 442 ms Content Transfer 4 ms

CDN & Delivery

Document on Cloudflare; assets also on Google Cloud CDN, Fastly, AWS CloudFront, Akamai

PASS

Document on Cloudflare; assets also on Google Cloud CDN, Fastly, AWS CloudFront, Akamai

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a51c5a767c5ed142-CDG

CDN cache status: DYNAMIC

Assets on Google Cloud CDN: cdn.shopify.com (assets: 9)

Got: via: 1.1 google

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

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

Assets on AWS CloudFront: cdn.attn.tv (assets: 4), cache Miss from cloudfront

Got: delegation duihxgfnjg37f.cloudfront.net

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

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

Assets on Akamai: cdn-widgetsrepository.yotpo.com (assets: 3)

Got: delegation dsa.cdn-widgetsrepository.yotpo.com.edgekey.net

Document served via CDN: Cloudflare

Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a51c5a767c5ed142-CDG

Asset hosts on a CDN

cdn.shopify.com — Google Cloud CDN · assets: 9
static.klaviyo.com — Fastly · assets: 7 · Cache Status: DYNAMIC
cdn.attn.tv — AWS CloudFront · assets: 4 · Cache Status: Miss from cloudfront
static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT
cdn-widgetsrepository.yotpo.com — Akamai · assets: 3

Other asset hosts

www.googletagmanager.com — assets: 3 · Google
connect.facebook.net — assets: 2 · below probe threshold
backend.alia-prod.com — assets: 1 · below probe threshold
s1.staq-cdn.com — assets: 1 · below probe threshold
shop.app — assets: 1 · below probe threshold
static-us.afterpay.com — assets: 1 · below probe threshold
static.rechargecdn.com — assets: 1 · below probe threshold

A+

CDN Cache Observability

Cache state: DYNAMIC

PASS

Cache state: DYNAMIC

CDN cache state observable via 1 header(s)

Got: cf-cache-status=DYNAMIC

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