Skip to content
https://scenegenerator.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
9
PASS
7
INFO
1
Probed from Madrid, Spain
200 OK
Checks
17
7 PASS 9 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.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 104.21.63.148: lookup 104.21.63.148: 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 172.67.147.30: lookup 172.67.147.30: 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 2606:4700:3030::6815:3f94: lookup 2606:4700:3030::6815:3f94: 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 2606:4700:3034::ac43:931e: lookup 2606:4700:3034::ac43:931e: 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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 200 Expected: 301 redirect to HTTPS

www / non-www

301https://www.scenegenerator.io/
200https://scenegenerator.io/

Preferred variant: non-www

HTTP → HTTPS

200http://scenegenerator.io/

HTTP version does not redirect to HTTPS

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

Certificate validity

77
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 & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a2b5317c7ab446a0-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: a2b5317c7ab446a0-CDG
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
2 A records, 256 ms lookup
PASS
2 A records, 256 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.63.148, 172.67.147.30
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3030::6815:3f94, 2606:4700:3034::ac43:931e
Info::
2 nameserver(s) configured
Got: bruce.ns.cloudflare.com, adrian.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (256 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 256 ms
A104.21.63.148, 172.67.147.30
AAAA2606:4700:3030::6815:3f94, 2606:4700:3034::ac43:931e
CNAME—
NSbruce.ns.cloudflare.com, adrian.ns.cloudflare.com
MX
5 route1.mx.cloudflare.net
37 route2.mx.cloudflare.net
37 route3.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.google.com ~all
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
google-site-verification=dNZRbZu9oYFrOwGbBqIWVO41pPM6bP8xbYYp6hWno4I
CAALookup not available with standard resolver
Resolved in 256 ms

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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 17ms across 3 resolvers (spread 21ms)
PASS
Mean 17ms across 3 resolvers (spread 21ms)
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1: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://scenegenerator.io

https://scenegenerator.io

427 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://scenegenerator.io200427 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3030::6815:3f94, 2606:4700:3034::ac43:931e
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3030::6815:3f94, 2606:4700:3034::ac43:931e Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 82 URLs
PASS
robots.txt present, sitemap with 82 URLs
Info::
robots.txt is present
Got: 2420 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 82 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2420 B Sitemaps referenced 1 User-agents ClaudeBot, Google-Extended, *, Amazonbot, CCBot, CloudflareBrowserRenderingCrawler, GPTBot, meta-externalagent, Applebot-Extended, Bytespider Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.
# use:      how AI systems may consume the content (immediate, reference, or full).

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no,use=reference
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

User-Agent: *
Allow: /
Disallow: /admin
Disallow: /zh/admin
Disallow: /settings
Disallow: /zh/settings
Disallow: /my-creations
Disallow: /zh/my-creations
Disallow: /sign-in
Disallow: /zh/sign-in
Disallow: /sign-up
Disallow: /zh/sign-up
Disallow: /forgot-password
Disallow: /zh/forgot-password
Disallow: /reset-password
Disallow: /zh/reset-password
Disallow: /verify-email
Disallow: /zh/verify-email
Disallow: /redeem-invite
Disallow: /zh/redeem-invite
Disallow: /auth-callback
Disallow: /zh/auth-callback
Disallow: /api/
Disallow: /*?*

Sitemap: https://scenegenerator.io/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 82 entries Valid XML Yes
Sample URLs:
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.
34 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 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.
440 ms
Total Time Total request time from DNS lookup through full response.
442 ms

Connection waterfall

DNS Lookup 34 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 367 ms Content Transfer 2 ms
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