Skip to content
https://starlink.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
6 PASS 2 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
TLS Certificate Expiry & Recommendations
41 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
A+
DNS Records
4 A records, 68 ms lookup
PASS
4 A records, 68 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.129.143, 151.101.1.143, 151.101.193.143, 151.101.65.143
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-38.azuregov-dns.us, ns2-38.azuregov-dns.us, ns3-38.azuregov-dns.us, ns4-38.azuregov-dns.us
Info::
1 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: 68 ms
Got: 68 ms
A151.101.129.143, 151.101.1.143, 151.101.193.143, 151.101.65.143
AAAA—
CNAME—
NSns1-38.azuregov-dns.us, ns2-38.azuregov-dns.us, ns3-38.azuregov-dns.us, ns4-38.azuregov-dns.us
MX
0 starlink-com.mail.protection.outlook.com
TXT
MS=ms69803613
teamviewer-sso-verification=76817d6b0ffa447c98b1084a75e3423a
google-site-verification=bmBSrVTdv3M1WWo5Mq6Vm0Pv1YKCgGDQMuXpUDvKROU
_globalsign-domain-verification=wzHziG-LuUZ3OsWXQdWlQ7DogwQ3fU5BOtWVLB47X4
apple-domain-verification=cMPCGom2zvRLHxMq
google-site-verification=C-TwJstx1-bUUG7adtToYdUKxFFmV_d7Sz4iny7r7Zk
NETORGFT5169410.onmicrosoft.com
_l4ml8bpvcxe1fpc4pmujtcoq0aopu29
SPF v=spf1 include:spf.protection.outlook.com ip4:167.89.70.193 -all
CAALookup not available with standard resolver
Resolved in 68 ms

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://starlink.com

https://starlink.com

17 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://starlink.com20017 msHTTP/1.1whydoyoucare?
A+
Crawlability
robots.txt present, sitemap with 182 URLs
PASS
robots.txt present, sitemap with 182 URLs
Info::
robots.txt is present
Got: 635 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 182 entries
Info::
Sitemap index with 182 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 635 B Sitemaps referenced 3 User-agents * Blocking No — crawling allowed
User-agent: *
Crawl-delay: 10

### Directories
Disallow: /browser-not-supported/
Disallow: /cookies-required/
Disallow: /404/
Disallow: /500/
Disallow: /invitation-invalid/
Disallow: /confirmation/
Disallow: /unsubscribe/
Disallow: /order/
Disallow: /new/

### Redirects
Disallow: /rv/
Disallow: /mobility/
Disallow: /maritime/
Disallow: /aviation/
Disallow: /case-studies/
Disallow: /fixed-site/
Disallow: /kit/
Disallow: /welcome/

### SITEMAPS
Sitemap: https://starlink.com/sitemaps/marketing/sitemap-index.xml
Sitemap: https://starlink.com/sitemaps/auth/sitemap.xml
Sitemap: https://starlink.com/sitemaps/support/sitemap-index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 182 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.starlink.com/
200https://starlink.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
starlink.com — via GoDaddy.com, LLC, 31 years old, hosted on Fastly
PASS
starlink.com — via GoDaddy.com, LLC, 31 years old, hosted on Fastly
Info::
Domain registered until Sep 7, 2026 (4 months remaining)
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: GoDaddy.com, 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: Fastly
Got: AS54113
Domain expiry

85 days

September 7, 2026

SSL certificate

41 days

Issued by Let's Encrypt

Domain age

31 years

Registered September 8, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.65.143

Registrar

GoDaddy.com, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created September 8, 1995 (31 years ago)
Expires September 7, 2026 (4 months)
Last Updated September 7, 2025
Name Servers ns1-38.azuregov-dns.us, ns2-38.azuregov-dns.us, ns3-38.azuregov-dns.us, ns4-38.azuregov-dns.us
DNSSEC Not enabled
Hosting
IP Address 151.101.65.143
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.1s)

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

A+
HTTP Probe Timing
Total 23 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.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
23 ms
Total Time Total request time from DNS lookup through full response.
24 ms

Connection waterfall

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