Skip to content
https://spaceship.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
Redirect Chain
1 redirect(s), 1230 ms total
REVIEW
1 redirect(s), 1230 ms total
Info::
Single redirect
Got: https://spaceship.com → https://www.spaceship.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1230 ms total
Got: 1230 ms

https://spaceship.com

515 ms · HTTP/1.1

301

https://www.spaceship.com/

715 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://spaceship.com301515 msHTTP/1.1namecheap-web
2https://www.spaceship.com/200715 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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
164 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

164
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
A+
DNS Records
1 A records, 33 ms lookup
PASS
1 A records, 33 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.54.117.246
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: launch2.spaceship.com, launch1.spaceship.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 33 ms
Got: 33 ms
A198.54.117.246
AAAA
CNAME
NSlaunch2.spaceship.com, launch1.spaceship.com
MX
0 mx1.spacemail.com
0 mx2.spacemail.com
TXT
SPF v=spf1 include:spf.spacemail.com include:sendgrid.net include:spf-ep-sps.jellyfi...
google-site-verification=cGoEwUUAG8dBZHrEBuEUVUBaM-9Iizuku6YD7jhVufY
ca3-a05f8a33ffa04e46b67793e58a532fb3
CAALookup not available with standard resolver
Resolved in 33 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

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 840 URLs
PASS
robots.txt present, sitemap with 840 URLs
Info::
robots.txt is present
Got: 46 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 840 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 46 B Sitemaps referenced 0 User-agents dotbot Blocking No — crawling allowed
User-agent: dotbot
Disallow: /
Crawl-delay: 1

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

403https://www.spaceship.com/
200https://spaceship.com/

HTTP → HTTPS

301http://spaceship.com/ https://www.spaceship.com/

Consistent

A+
Domain Intelligence
spaceship.com — via Spaceship, Inc., 30 years, 7 months old, hosted on Namecheap
PASS
spaceship.com — via Spaceship, Inc., 30 years, 7 months old, hosted on Namecheap
Info::
Domain registered until Feb 4, 2027 (9 months remaining)
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: Namecheap
Got: AS22612
Domain expiry

203 days

February 4, 2027

SSL certificate

164 days

Issued by Sectigo Limited

Domain age

30 years, 7 months

Registered February 3, 1996

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Namecheap

ASN AS22612

198.54.117.246

Registrar

Spaceship, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Spaceship, Inc.
Created February 3, 1996 (30 years, 7 months ago)
Expires February 4, 2027 (9 months)
Last Updated April 9, 2026
Name Servers launch1.spaceship.com, launch2.spaceship.com
DNSSEC Enabled
Hosting
IP Address 198.54.117.246
ASN AS22612 (NAMECHEAP-NET - Namecheap, Inc., US)
Provider Namecheap
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 33 ms TCP Connect 174 ms TLS Handshake 177 ms Server Processing 174 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback