Skip to content
https://ratemyscene.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
7 PASS 9 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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 159.195.214.187 does not match any cert SAN: v2202608391578493161.goodsrv.de
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

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.ratemyscene.com/
200https://ratemyscene.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://ratemyscene.com/ → https://ratemyscene.com/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 873 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
12 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
164 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
173 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
544 ms
Total Time Total request time from DNS lookup through full response.
874 ms

Connection waterfall

DNS Lookup 12 ms TCP Connect 164 ms TLS Handshake 173 ms Server Processing 195 ms Content Transfer 330 ms
B
TLS Certificate Expiry & Recommendations
84 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

84
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
1 A records, 14 ms lookup
PASS
1 A records, 14 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 159.195.214.187
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns1.vercel-dns.com, ns2.vercel-dns.com
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: 14 ms
Got: 14 ms
A159.195.214.187
AAAA—
CNAME—
NSns1.vercel-dns.com, ns2.vercel-dns.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 14 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
CAA Records
issue: letsencrypt.org, pki.goog, sectigo.com
PASS
issue: letsencrypt.org, pki.goog, sectigo.com
Info::
CAA issue tag present — authorized CA(s): letsencrypt.org, pki.goog, sectigo.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 15ms across 3 resolvers (spread 23ms)
PASS
Mean 15ms across 3 resolvers (spread 23ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 14ms
Got: 14ms via 8.8.8.8:53
Info::
Quad9: 27ms
Got: 27ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://ratemyscene.com

https://ratemyscene.com

760 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ratemyscene.com200760 msHTTP/1.1
A+
Crawlability
robots.txt present, sitemap with 11467 URLs
PASS
robots.txt present, sitemap with 11467 URLs
Info::
robots.txt is present
Got: 229 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11467 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 229 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /admin/
Disallow: /api/
Disallow: /calendar
Disallow: /login
Disallow: /register
Disallow: /search
Disallow: /taste-dna

Host: https://ratemyscene.com
Sitemap: https://ratemyscene.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 11467 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ratemyscene.com — via Name.com, Inc., 13 days old, hosted on netcup-AS - netcup GmbH, DE
PASS
ratemyscene.com — via Name.com, Inc., 13 days old, hosted on netcup-AS - netcup GmbH, DE
Info::
Domain registered until Jul 26, 2027 (11 months remaining)
Info::
Domain is only 13 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Jul 26, 2026
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: Name.com, 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: netcup-AS - netcup GmbH, DE
Got: AS197540
Domain expiry

344 days

July 26, 2027

SSL certificate

84 days

Issued by Let's Encrypt

Domain age

13 days

Registered July 26, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

netcup-AS - netcup GmbH, DE

ASN AS197540

159.195.214.187

Registrar

Name.com, Inc.

Unlocked 2 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Name.com, Inc.
Created July 26, 2026 (13 days ago)
Expires July 26, 2027 (11 months)
Last Updated July 26, 2026
Name Servers ns1.vercel-dns.com, ns2.vercel-dns.com
DNSSEC Not enabled
Hosting
IP Address 159.195.214.187
ASN AS197540 (netcup-AS - netcup GmbH, DE)
Provider netcup-AS - netcup GmbH, DE
Data source: rdap (0.2s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

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

Send Feedback