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 Sao Paulo, Brazil

307 Temporary Redirect

Checks

5 PASS 10 REVIEW 1 FIX

Redirect Chain

Action

2 redirect(s), 3323 ms total

FIX

2 redirect(s), 3323 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

Redirect overhead: 3323 ms total

Got: 3323 ms

https://nfventurestudio.netlify.app

688 ms · HTTP/1.1

307

https://nfventurestudio.netlify.app/app/...

2131 ms · HTTP/1.1

307

https://nfventurestudio.netlify.app/logi...

504 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://nfventurestudio.netlify.app	307	688 ms	HTTP/1.1	Netlify
2	https://nfventurestudio.netlify.app/app/...	307	2131 ms	HTTP/1.1	Netlify
3	https://nfventurestudio.netlify.app/logi...	200	504 ms	HTTP/1.1	Netlify

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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 54.232.119.62 does not match any cert SAN: ec2-54-232-119-62.sa-east-1.compute.amazonaws.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 2600:1f1e:7c1:c300::258: lookup 2600:1f1e:7c1:c300::258: 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

Mean 39ms across 3 resolvers (spread 106ms)

REVIEW

Mean 39ms across 3 resolvers (spread 106ms)

Quad9: 4ms

Got: 4ms via 9.9.9.9:53

Cloudflare: 5ms

Got: 5ms via 1.1.1.1:53

Google: 110ms

Got: 110ms via 8.8.8.8:53

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.

HTTP Probe Timing

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

REVIEW

DNS Lookup

6 ms

TCP Connect

2 ms

TLS Handshake

4 ms

Time to First Byte

984 ms

Total Time

984 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 2 ms TLS Handshake 4 ms Server Processing 971 ms Content Transfer 0 ms

TLS Certificate Expiry & Recommendations

167 days until leaf cert expires — 2 issues to address

REVIEW

Certificate validity

167

days left

0d 30d 60d 90d+

Recommended actions

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

Netlify ("Netlify Durable"; fwd=bypass)

REVIEW

Netlify ("Netlify Durable"; fwd=bypass)

Document is served via Netlify CDN

Got: delegation nfventurestudio.netlify.app

CDN cache status: "Netlify Durable"; fwd=bypass

Document served via CDN: Netlify

Provider Netlify Cache Status "Netlify Durable"; fwd=bypass Evidence delegation nfventurestudio.netlify.app

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

DNS Records

1 A records, 20 ms lookup

PASS

1 A records, 20 ms lookup

Resolves to 1 IPv4 address(es)

Got: 54.232.119.62

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2600:1f1e:7c1:c300::258

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: 20 ms

Got: 20 ms

A	54.232.119.62
AAAA	2600:1f1e:7c1:c300::258
CNAME	—
NS	—
MX	—
TXT	—
CAA	Lookup not available with standard resolver

Resolved in 20 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+

IPv6 Readiness

IPv6 reachable (5 ms)

PASS

IPv6 reachable (5 ms)

IPv6 is configured and reachable at 2600:1f1e:7c1:c300::258

Got: 5 ms connect

IPv6 Ready

AAAA Records 2600:1f1e:7c1:c300::258 Connection Reachable (5 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

https://www.nfventurestudio.netlify.app/

200https://nfventurestudio.netlify.app/

HTTP → HTTPS

301http://nfventurestudio.netlify.app/ → https://nfventurestudio.netlify.app/

Consistent

A+

CDN Cache Observability

Cache state: Age=1s

PASS

Cache state: Age=1s

CDN cache state observable via 1 header(s)

Got: age=1

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed

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