Skip to content
https://startpage.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
303 HTTP 303
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.

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 301-redirects to HTTPS

www / non-www

200https://www.startpage.com/
200https://startpage.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://startpage.com/ https://startpage.com:443/

Consistent

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

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 7 ms lookup
PASS
1 A records, 7 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 67.63.52.231
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
Info::
5 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: 7 ms
Got: 7 ms
A67.63.52.231
AAAA
CNAME
NSdns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
docusign=4aa04a43-5af3-4b1b-8b86-fb027c1d5de7canva-site-verification=SQqtO91fxFT...
google-site-verification=0C93wk5LSLM-lamfw7DTbObpX_J8MDpxj8B0nP6t30g
google-site-verification=g8vFaNLgbWlSgUp3k3bEVjZyaJt3t1llocCZBZAHUYU
google-site-verification=uylcKpM8QSGvtnQ90O0RUJqI4pqr3mndH-krbYpc2kA
SPF v=spf1 include:spf.mailjet.com include:_spf.google.com include:mail.zendesk.com ...
CAALookup not available with standard resolver
Resolved in 7 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
Redirect Chain
1 redirect(s), 277 ms total
PASS
1 redirect(s), 277 ms total
Info::
Single redirect
Got: https://startpage.com → https://www.startpage.com/ (303)
Info::
WWW normalization redirect

https://startpage.com

79 ms · HTTP/1.1

303

https://www.startpage.com/

198 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://startpage.com30379 msHTTP/1.1nginx
2https://www.startpage.com/200198 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 188 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

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 188 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /sp/cdn/images/
Allow: /sp/cdn/favicons/
Disallow: /cgi-bin/
Disallow: /do/
Disallow: /sp/
Disallow: /av/
Noindex: /cgi-bin/
Noindex: /do/
Noindex: /sp/
Noindex: /av/

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A+
Domain Intelligence
startpage.com — via eNom, LLC, 28 years, 11 months old, hosted on AWS
PASS
startpage.com — via eNom, LLC, 28 years, 11 months old, hosted on AWS
Info::
Domain registered until Oct 10, 2028 (2 years, 6 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: eNom, LLC
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

847 days

October 10, 2028

SSL certificate

202 days

Issued by GoGetSSL

Domain age

28 years, 11 months

Registered October 11, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

67.63.52.231

Registrar

eNom, LLC

Unlocked 4 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 eNom, LLC
Created October 11, 1997 (28 years, 11 months ago)
Expires October 10, 2028 (2 years, 6 months)
Last Updated April 5, 2023
Name Servers dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net
DNSSEC Enabled
Hosting
IP Address 67.63.52.231
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 23 ms TLS Handshake 27 ms Server Processing 23 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