Skip to content
https://bestreviews.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
Reverse DNS
0/3 IPs match cert SAN
REVIEW
0/3 IPs match cert SAN
Info::
PTR for 50.112.243.135 does not match any cert SAN: ec2-50-112-243-135.us-west-2.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 for 54.148.218.24 does not match any cert SAN: ec2-54-148-218-24.us-west-2.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 for 52.33.229.90 does not match any cert SAN: ec2-52-33-229-90.us-west-2.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.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
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

B
TLS Certificate Expiry & Recommendations
80 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

80
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
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.
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
3 A records, 16 ms lookup
PASS
3 A records, 16 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 50.112.243.135, 54.148.218.24, 52.33.229.90
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1353.awsdns-41.org, ns-1708.awsdns-21.co.uk, ns-507.awsdns-63.com, ns-542.awsdns-03.net
Info::
6 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 16 ms
Got: 16 ms
A50.112.243.135, 54.148.218.24, 52.33.229.90
AAAA—
CNAME—
NSns-1353.awsdns-41.org, ns-1708.awsdns-21.co.uk, ns-507.awsdns-63.com, ns-542.awsdns-03.net
MX
0 bestreviews-com.mail.protection.outlook.com
10 aspmx.l.google.com
20 alt2.aspmx.l.google.com
20 alt1.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx2.googlemail.com
TXT
MS=ms97065226TTL
google-site-verification=-8pune6dt4GZ1EsIdQJk0CvRu0Cf9p730QCe2AYFqws
google-site-verification=gVHzbGSwtMgeFdeqX0mCbs7uw5kyu1pxc5KT6BCxCUw
google-site-verification=pk7fkOIVgFDT6wyyDs35YIwhfPX0v7MJPXc6aWBHJkE
SPF v=spf1 include:spf.protection.outlook.com -all
CAALookup not available with standard resolver
Resolved in 16 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A
CAA Records
issue: amazon.com, amazonaws.com, amazontrust.com, awstrust.com, digicert.com
PASS
issue: amazon.com, amazonaws.com, amazontrust.com, awstrust.com, digicert.com
Info::
CAA issue tag present — authorized CA(s): amazon.com, amazonaws.com, amazontrust.com, awstrust.com, digicert.com
Info::
No CAA iodef tag — won't be notified of failed issuance attempts
Add `0 iodef "mailto:security@example.com"` to receive notifications when a CA refuses issuance because it doesn't match your CAA policy. Useful signal for detecting issuance attempts by unauthorized CAs.
A+
Multi-Resolver DNS Speed
Mean 7ms across 3 resolvers (spread 7ms)
PASS
Mean 7ms across 3 resolvers (spread 7ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 8ms
Got: 8ms via 9.9.9.9:53
Info::
Google: 11ms
Got: 11ms 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://bestreviews.com

https://bestreviews.com

434 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://bestreviews.com200434 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 22357 URLs
PASS
robots.txt present, sitemap with 22357 URLs
Info::
robots.txt is present
Got: 212 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 22357 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 212 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://bestreviews.com/sitemap.xml
Sitemap: https://bestreviews.com/sitemap-image.xml
Sitemap: https://bestreviews.com/sitemap-video.xml
Disallow: /ca/*
Disallow: *?q=
Disallow: *?letter=
sitemap.xml 200 OK
Type URL Set URLs 22357 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::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.bestreviews.com/
200https://bestreviews.com/

Preferred variant: non-www

HTTP → HTTPS

301http://bestreviews.com/ → https://bestreviews.com:443/

Consistent

A+
Domain Intelligence
bestreviews.com — via CSC Corporate Domains, Inc., 23 years, 11 months old, hosted on AWS
PASS
bestreviews.com — via CSC Corporate Domains, Inc., 23 years, 11 months old, hosted on AWS
Info::
Domain registered until Jan 1, 2027 (4 months remaining)
Info::
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.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

137 days

January 1, 2027

SSL certificate

80 days

Issued by Amazon

Domain age

23 years, 11 months

Registered January 1, 2003

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.33.229.90

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 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 CSC Corporate Domains, Inc.
Created January 1, 2003 (23 years, 11 months ago)
Expires January 1, 2027 (4 months)
Last Updated December 28, 2025
Name Servers ns-1353.awsdns-41.org, ns-1708.awsdns-21.co.uk, ns-507.awsdns-63.com, ns-542.awsdns-03.net
DNSSEC Not enabled
Hosting
IP Address 52.33.229.90
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

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 442 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
21 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
417 ms
Total Time Total request time from DNS lookup through full response.
443 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 21 ms TLS Handshake 23 ms Server Processing 366 ms Content Transfer 26 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback