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

6 PASS 11 REVIEW

DNS Records

2 A records, 27 ms lookup

REVIEW

2 A records, 27 ms lookup

Resolves to 2 IPv4 address(es)

Got: 172.66.3.8, 162.159.143.12

No IPv6 (AAAA) records

CNAME record at zone apex

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Got: cdn3.wixdns.net

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 time: 27 ms

Got: 27 ms

A	172.66.3.8, 162.159.143.12
AAAA	—
CNAME	cdn3.wixdns.net
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 27 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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

REVIEW

0/2 IPs match cert SAN

PTR lookup failed for 172.66.3.8: lookup 172.66.3.8: 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 162.159.143.12: lookup 162.159.143.12: 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.

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

38 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, AWS CloudFront

REVIEW

Document on Cloudflare; assets also on Fastly, AWS CloudFront

Document is served via Cloudflare CDN (edge: CDG)

Got: cf-ray: a4d8f738af796cb2-CDG

Assets on Fastly: static.parastorage.com (assets: 44), cache HIT

Got: x-served-by: cache-toj-leto2350048-TOJ

Assets on AWS CloudFront: static.wixstatic.com (assets: 33), cache Hit from cloudfront

Got: delegation d1cq301dpr7fww.cloudfront.net

Document served via CDN: Cloudflare

Provider Cloudflare Evidence cf-ray: a4d8f738af796cb2-CDG

Asset hosts on a CDN

static.parastorage.com — Fastly · assets: 44 · Cache Status: HIT
static.wixstatic.com — AWS CloudFront · assets: 33 · Cache Status: Hit from cloudfront

Other asset hosts

pagead2.googlesyndication.com — assets: 4 · Google
browser.sentry-cdn.com — assets: 2 · 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.

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

A+

Subdomain Takeover

No subdomain takeover risk detected

PASS

No subdomain takeover risk detected

CNAME does not point at a known takeover-able service

A+

Multi-Resolver DNS Speed

Mean 42ms across 3 resolvers (spread 24ms)

PASS

Mean 42ms across 3 resolvers (spread 24ms)

Google: 30ms

Got: 30ms via 8.8.8.8:53

Quad9: 42ms

Got: 42ms via 9.9.9.9:53

Cloudflare: 54ms

Got: 54ms via 1.1.1.1:53

A+

Redirect Chain

0 redirect(s), 68 ms total

PASS

0 redirect(s), 68 ms total

https://www.ferdowsspa.com

68 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://www.ferdowsspa.com	403	68 ms	HTTP/1.1	cloudflare

A+

URL Variants

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

PASS

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

www/non-www redirect configured correctly (preferred: www)

HTTP correctly redirects to HTTPS permanently

Got: HTTP 301

www / non-www

200https://www.ferdowsspa.com/

301https://ferdowsspa.com/

Preferred variant: www

HTTP → HTTPS

301http://www.ferdowsspa.com/ → https://www.ferdowsspa.com/

Consistent

A+

Domain Intelligence

ferdowsspa.com — via Wix.com Ltd., 3 years, 2 months old, hosted on wix_com - Wix.com Ltd., IL

PASS

ferdowsspa.com — via Wix.com Ltd., 3 years, 2 months old, hosted on wix_com - Wix.com Ltd., IL

Domain registered until Aug 14, 2027 (9 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: Wix.com Ltd.

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: wix_com - Wix.com Ltd., IL

Got: AS58182

Domain expiry

297 days

August 14, 2027

SSL certificate

38 days

Issued by Google Trust Services

Domain age

3 years, 2 months

Registered August 14, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

wix_com - Wix.com Ltd., IL

ASN AS58182

185.230.63.171

Registrar

Wix.com Ltd.

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 Wix.com Ltd.

Created August 14, 2023 (3 years, 2 months ago)

Expires August 14, 2027 (9 months)

Last Updated July 1, 2026

Name Servers ns8.wixdns.net, ns9.wixdns.net

DNSSEC Not enabled

Hosting

IP Address 185.230.63.171

ASN AS58182 (wix_com - Wix.com Ltd., IL)

Provider wix_com - Wix.com Ltd., IL

Data source: rdap (0.5s)

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

PASS

DNS Lookup

57 ms

TCP Connect

17 ms

TLS Handshake

25 ms

Time to First Byte

131 ms

Total Time

132 ms

Connection waterfall

DNS Lookup 57 ms TCP Connect 17 ms TLS Handshake 25 ms Server Processing 33 ms Content Transfer 1 ms

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