Skip to content
https://mushirai.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
10
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
6 PASS 10 REVIEW 1 FIX
D
HTTP Probe Timing
Action
Total 2456 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
83 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.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
2.45 s
Total Time Total request time from DNS lookup through full response.
2.46 s

Connection waterfall

DNS Lookup 83 ms TCP Connect 17 ms TLS Handshake 38 ms Server Processing 2.31 s Content Transfer 8 ms
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR for 185.158.133.1 does not match any cert SAN: lovable-app-cd-1-4.p.l5e.io
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
Multi-Resolver DNS Speed
Action
Mean 276ms across 3 resolvers (spread 284ms)
REVIEW
Mean 276ms across 3 resolvers (spread 284ms)
Info::
Google: 180ms
Got: 180ms via 8.8.8.8:53
Info::
Quad9: 186ms
Got: 186ms via 9.9.9.9:53
Info::
Cloudflare: 464ms
Got: 464ms via 1.1.1.1:53
Info::
High latency spread between resolvers: 284ms (min 180ms / max 464ms)
Wide gap between the fastest and slowest public resolver suggests a geographic anycast issue or an authoritative-server cache problem. Users in different regions will see materially different DNS times.
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
URL Variants
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
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.mushirai.com/
200https://mushirai.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://mushirai.com/ → https://mushirai.com/

Consistent

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

Certificate validity

47
days left
0d 30d 60d 90d+

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a38ec33d6aa6d140-CDG
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a38ec33d6aa6d140-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
1 A records, 180 ms lookup
PASS
1 A records, 180 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 185.158.133.1
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: launch1.spaceship.net, launch2.spaceship.net
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 180 ms
Got: 180 ms
A185.158.133.1
AAAA—
CNAME—
NSlaunch1.spaceship.net, launch2.spaceship.net
MX
0 mx2.efwd.spaceship.net
0 mx1.efwd.spaceship.net
TXT
google-site-verification=EEUscLYguvkwsOjfvAs_w6KW4BQ0cugVMBTYOnHaFLE
SPF v=spf1 include:spf.efwd.spaceship.net ~all
CAALookup not available with standard resolver
Resolved in 180 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
DNSSEC
Signed and validating
PASS
Signed and validating
Info::
DNSSEC fully signed and chain validates (ECDSAP256SHA256)
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://mushirai.com

https://mushirai.com

2445 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mushirai.com2002445 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 26 URLs
PASS
robots.txt present, sitemap with 26 URLs
Info::
robots.txt is present
Got: 317 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 26 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 317 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /admin
Disallow: /admin/
Disallow: /auth
Disallow: /auth/
Disallow: /reset-password
Disallow: /dashboard
Disallow: /workspace
Disallow: /project
Disallow: /billing
Disallow: /idea-report
Disallow: /api
Disallow: /.mcp
Disallow: /.well-known

Sitemap: https://mushirai.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 26 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
mushirai.com — via Spaceship, Inc., 1 months old, hosted on Cloudflare
PASS
mushirai.com — via Spaceship, Inc., 1 months old, hosted on Cloudflare
Info::
Domain registered until Jul 29, 2027 (10 months remaining)
Info::
Domain is only 1 months 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 29, 2026
Info::
DNSSEC is enabled
Info::
Registrar: Spaceship, 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: Cloudflare
Got: AS13335
Domain expiry

321 days

July 29, 2027

SSL certificate

47 days

Issued by Google Trust Services

Domain age

1 months

Registered July 29, 2026

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

185.158.133.1

Registrar

Spaceship, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Spaceship, Inc.
Created July 29, 2026 (1 months ago)
Expires July 29, 2027 (10 months)
Last Updated July 29, 2026
Name Servers launch1.spaceship.net, launch2.spaceship.net
DNSSEC Enabled
Hosting
IP Address 185.158.133.1
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.3s)

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.

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