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
90
GRADE
A
FIX
0
REVIEW
7
PASS
9
INFO
1
Probed from Sao Paulo, Brazil
200 OK
Checks
17
9 PASS 7 REVIEW
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/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
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.
Info::
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.
B
Multi-Resolver DNS Speed
Mean 39ms across 3 resolvers (spread 102ms)
REVIEW
Mean 39ms across 3 resolvers (spread 102ms)
Info::
Cloudflare: 5ms
Got: 5ms via 1.1.1.1:53
Info::
Google: 7ms
Got: 7ms via 8.8.8.8:53
Info::
Quad9: 107ms
Got: 107ms via 9.9.9.9:53
B
TLS Certificate Expiry & Recommendations
171 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

171
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
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
1 A records, 17 ms lookup
PASS
1 A records, 17 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 54.232.119.62
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2600:1f1e:7c1:c300::258
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: 17 ms
Got: 17 ms
A54.232.119.62
AAAA2600:1f1e:7c1:c300::258
CNAME—
NS—
MX—
TXT—
CAALookup 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

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+
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

473 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://marriage10.netlify.app200473 msHTTP/1.1Netlify
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2600:1f1e:7c1:c300::258
Got: 2 ms connect
IPv6 Ready
AAAA Records 2600:1f1e:7c1:c300::258 Connection Reachable (2 ms)
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 21 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
21 ms
Total Time Total request time from DNS lookup through full response.
22 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 3 ms TLS Handshake 5 ms Server Processing 5 ms Content Transfer 1 ms
A+
CDN & Delivery
Netlify ("Netlify Edge"; hit; ttl=31535770)
PASS
Netlify ("Netlify Edge"; hit; ttl=31535770)
Info::
Document is served via Netlify CDN
Got: delegation marriage10.netlify.app
Info::
CDN cache status: "Netlify Edge"; hit; ttl=31535770
Document served via CDN: Netlify
Provider Netlify Cache Status "Netlify Edge"; hit; ttl=31535770 Evidence delegation marriage10.netlify.app
A+
CDN Cache Observability
Cache state: Age=231s
PASS
Cache state: Age=231s
Info::
CDN cache state observable via 1 header(s)
Got: age=231
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