Skip to content
https://d3g3kq4d6y6c79.cloudfront.net

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
7
PASS
8
INFO
1
Probed from Santa Clara, United States
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:9000:204d:a000:8:34a3:5140:21, 2600:9000:204d:c600:8:34a3:5140:21, 2600:9000:204d:3800:8:34a3:5140:21, 2600:9000:204d:4a00:8:34a3:5140:21, 2600:9000:204d:7c00:8:34a3:5140:21, 2600:9000:204d:ee00:8:34a3:5140:21, 2600:9000:204d:9200:8:34a3:5140:21, 2600:9000:204d:6800:8:34a3:5140:21
Info::
IPv6 connection error
Got: dial tcp6 [2600:9000:204d:a000:8:34a3:5140:21]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2600:9000:204d:a000:8:34a3:5140:21, 2600:9000:204d:c600:8:34a3:5140:21, 2600:9000:204d:3800:8:34a3:5140:21, 2600:9000:204d:4a00:8:34a3:5140:21, 2600:9000:204d:7c00:8:34a3:5140:21, 2600:9000:204d:ee00:8:34a3:5140:21, 2600:9000:204d:9200:8:34a3:5140:21, 2600:9000:204d:6800:8:34a3:5140:21 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/12 IPs match cert SAN
REVIEW
0/12 IPs match cert SAN
Info::
PTR for 65.8.44.218 does not match any cert SAN: server-65-8-44-218.sfo53.r.cloudfront.net
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 65.8.44.51 does not match any cert SAN: server-65-8-44-51.sfo53.r.cloudfront.net
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 65.8.44.176 does not match any cert SAN: server-65-8-44-176.sfo53.r.cloudfront.net
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 65.8.44.46 does not match any cert SAN: server-65-8-44-46.sfo53.r.cloudfront.net
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:9000:204d:a000:8:34a3:5140:21: lookup 2600:9000:204d:a000:8:34a3:5140:21: 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:9000:204d:c600:8:34a3:5140:21: lookup 2600:9000:204d:c600:8:34a3:5140:21: 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:9000:204d:3800:8:34a3:5140:21: lookup 2600:9000:204d:3800:8:34a3:5140:21: 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:9000:204d:4a00:8:34a3:5140:21: lookup 2600:9000:204d:4a00:8:34a3:5140:21: 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:9000:204d:7c00:8:34a3:5140:21: lookup 2600:9000:204d:7c00:8:34a3:5140:21: 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:9000:204d:ee00:8:34a3:5140:21: lookup 2600:9000:204d:ee00:8:34a3:5140:21: 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:9000:204d:9200:8:34a3:5140:21: lookup 2600:9000:204d:9200:8:34a3:5140:21: 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:9000:204d:6800:8:34a3:5140:21: lookup 2600:9000:204d:6800:8:34a3:5140:21: 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
HTTP Probe Timing
Total 877 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
26 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
4 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.
600 ms
Total Time Total request time from DNS lookup through full response.
878 ms

Connection waterfall

DNS Lookup 26 ms TCP Connect 4 ms TLS Handshake 5 ms Server Processing 564 ms Content Transfer 278 ms
B
TLS Certificate Expiry & Recommendations
58 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

58
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
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
4 A records, 30 ms lookup
PASS
4 A records, 30 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.44.218, 65.8.44.51, 65.8.44.176, 65.8.44.46
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:204d:a000:8:34a3:5140:21, 2600:9000:204d:c600:8:34a3:5140:21, 2600:9000:204d:3800:8:34a3:5140:21, 2600:9000:204d:4a00:8:34a3:5140:21, 2600:9000:204d:7c00:8:34a3:5140:21, 2600:9000:204d:ee00:8:34a3:5140:21, 2600:9000:204d:9200:8:34a3:5140:21, 2600:9000:204d:6800:8:34a3:5140:21
Info::
4 nameserver(s) configured
Got: ns-1316.awsdns-36.org, ns-1805.awsdns-33.co.uk, ns-472.awsdns-59.com, ns-570.awsdns-07.net
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: 30 ms
Got: 30 ms
A65.8.44.218, 65.8.44.51, 65.8.44.176, 65.8.44.46
AAAA2600:9000:204d:a000:8:34a3:5140:21, 2600:9000:204d:c600:8:34a3:5140:21, 2600:9000:204d:3800:8:34a3:5140:21, 2600:9000:204d:4a00:8:34a3:5140:21, 2600:9000:204d:7c00:8:34a3:5140:21, 2600:9000:204d:ee00:8:34a3:5140:21, 2600:9000:204d:9200:8:34a3:5140:21, 2600:9000:204d:6800:8:34a3:5140:21
CNAME—
NSns-1316.awsdns-36.org, ns-1805.awsdns-33.co.uk, ns-472.awsdns-59.com, ns-570.awsdns-07.net
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 30 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 12ms across 3 resolvers (spread 22ms)
PASS
Mean 12ms across 3 resolvers (spread 22ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 7ms
Got: 7ms via 9.9.9.9:53
Info::
Google: 26ms
Got: 26ms 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://d3g3kq4d6y6c79.cloudfront.net

https://d3g3kq4d6y6c79.cloudfront.net

562 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://d3g3kq4d6y6c79.cloudfront.net200562 msHTTP/1.1AmazonS3
A+
Crawlability
robots.txt present, sitemap with 14 URLs
PASS
robots.txt present, sitemap with 14 URLs
Info::
robots.txt is present
Got: 74 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 14 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 74 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /

Sitemap: https://everhavencare.com.au/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 14 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 301-redirects to HTTPS

www / non-www

https://www.d3g3kq4d6y6c79.cloudfront.net/
200https://d3g3kq4d6y6c79.cloudfront.net/

HTTP → HTTPS

301http://d3g3kq4d6y6c79.cloudfront.net/ → https://d3g3kq4d6y6c79.cloudfront.net/

Consistent

A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: SFO53-P10)
Got: x-amz-cf-id: GACzbhNnxn0GWzi874tkxOYvgr6-1UiXzUqIcXRT1UZkOcv_n2BOJA==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: GACzbhNnxn0GWzi874tkxOYvgr6-1UiXzUqIcXRT1UZkOcv_n2BOJA==
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 1 header(s)
Got: x-cache=Miss from cloudfront
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