Skip to content
https://marriage10.netlify.app

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
7
PASS
8
INFO
1
Probed from New York, United Stated
200 OK
Checks
17
8 PASS 7 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
Info::
IPv6 connection error
Got: dial tcp6 [2600:1f18:16e:df01::258]:443: connect: no route to host
IPv6 Misconfigured
AAAA Records 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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 18.208.88.157 does not match any cert SAN: ec2-18-208-88-157.compute-1.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.
Info::
PTR for 98.84.224.111 does not match any cert SAN: ec2-98-84-224-111.compute-1.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.
Info::
PTR lookup failed for 2600:1f18:16e:df01::258: lookup 2600:1f18:16e:df01::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.
Info::
PTR lookup failed for 2600:1f18:16e:df01::259: lookup 2600:1f18:16e:df01::259: 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.
B
TLS Certificate Expiry & Recommendations
173 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

173
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
B
CDN & Delivery
Netlify ("Netlify Edge"; fwd=stale; fwd-status=200; stored)
REVIEW
Netlify ("Netlify Edge"; fwd=stale; fwd-status=200; stored)
Info::
Document is served via Netlify CDN
Got: delegation marriage10.netlify.app
Info::
CDN cache status: "Netlify Edge"; fwd=stale; fwd-status=200; stored
Document served via CDN: Netlify
Provider Netlify Cache Status "Netlify Edge"; fwd=stale; fwd-status=200; stored Evidence delegation marriage10.netlify.app
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: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A
DNS Records
2 A records, 19 ms lookup
PASS
2 A records, 19 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 18.208.88.157, 98.84.224.111
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 19 ms
Got: 19 ms
A18.208.88.157, 98.84.224.111
AAAA2600:1f18:16e:df01::258, 2600:1f18:16e:df01::259
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 19 ms

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
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 5ms across 3 resolvers (spread 8ms)
PASS
Mean 5ms across 3 resolvers (spread 8ms)
Info::
Quad9: 2ms
Got: 2ms via 9.9.9.9:53
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 10ms
Got: 10ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://marriage10.netlify.app

https://marriage10.netlify.app

58 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://marriage10.netlify.app20058 msHTTP/1.1Netlify
A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 72 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 72 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Sitemap: https://www.yourdomain.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 8 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.marriage10.netlify.app/
200https://marriage10.netlify.app/

HTTP → HTTPS

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

Consistent

A+
HTTP Probe Timing
Total 92 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
8 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
81 ms
Total Time Total request time from DNS lookup through full response.
93 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 8 ms TLS Handshake 10 ms Server Processing 58 ms Content Transfer 12 ms
A+
CDN Cache Observability
Cache state: fresh (Age=0)
PASS
Cache state: fresh (Age=0)
Info::
CDN cache state observable via 1 header(s)
Got: age=0
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.

Send Feedback