Skip to content
https://sas.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
77
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Crawlability
Action
robots.txt present, sitemap with 37705 URLs
FIX
robots.txt present, sitemap with 37705 URLs
Info::
robots.txt is present
Got: 3845 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 37705 entries
Info::
robots.txt references sitemap

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more ▾

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

robots.txt 200 OK
Size 3845 B Sitemaps referenced 3 User-agents Baiduspider, AhrefsBot, Amazonbot, *, Duckduckbot, Moz, facebookexternalhit, Twitterbot, Slackbot, Pinterestbot, Anthropic-AI, CCBot, Googlebot, Bingbot, Slurp, YandexBot, SemrushBot, MJ12Bot, PerplexityBot, Bytespider, LinkedInBot, GPTBot, Applebot, SiteimproveBot Blocking Yes — all crawlers blocked
#

# robots.txt file for www.sas.com

#

User-agent: Googlebot

User-agent: Bingbot

User-agent: Duckduckbot

User-agent: Slurp

User-agent: Baiduspider

User-agent: YandexBot

User-agent: AhrefsBot

User-agent: SemrushBot

User-agent: Moz

User-agent: MJ12Bot

User-agent: facebookexternalhit

User-agent: Twitterbot

User-agent: LinkedInBot

User-agent: Slackbot

User-agent: Pinterestbot

User-agent: GPTBot

User-agent: Anthropic-AI

User-agent: CCBot

User-agent: PerplexityBot

User-agent: Bytespider

User-agent: Amazonbot

User-agent: Applebot

User-agent: SiteimproveBot

Disallow: /content/sascom/

Disallow: /apps/

Disallow: /ctx/

Disallow: /mv/

Disallow: /adminapps1/

Disallow: /adminapps2/

Disallow: /adminapps3/

Disallow: /adminapps4/

Disallow: /analystconf/

Disallow: /bin/f2f.cgi

Disallow: /bin/broker2

Disallow: /events/sasforuminternational/schedulebuilder/

Disallow: /bin/broker

Disallow: /forums/

Disallow: /images/email/

Disallow: /onlinedoc/

Disallow: /usergroups/sasforuminternational/call/

Disallow: /usergroups/sasforuminternational/proceedings/

Disallow: /usergroups/seugi/call/

Disallow: /search/

Disallow: /reg/

Disallow: /store/

Disallow: /contract/

Disallow: /pstest/

Disallow: /offices/europe/germany/css/

Disallow: /offices/europe/germany/curated/

Disallow: /offices/europe/germany/download/

Disallow: /offices/europe/germany/email/

Disallow: /offices/europe/germany/forms/

Disallow: /offices/europe/germany/includes/

Disallow: /offices/europe/germany/internal_use/

Disallow: /offices/europe/germany/kampagnen/ressources/download/pdf/

Disallow: /offices/europe/germany/popup/

Disallow: /offices/europe/germany/surveys/

Disallow: /offices/europe/germany/commerzbank/

Disallow: /reg/gen/de/commerzbank_sas

Disallow: /offices/europe/slovakia/sig/

Disallow: /offices/europe/greece/sig/

Disallow: /offices/europe/czech/sig/

Disallow: /offices/europe/france/pdf/

Disallow: /offices/europe/france/css/

Disallow: /offices/europe/france/mailing/

Disallow: /offices/europe/france/newsletter/

Disallow: /offices/europe/france/lib/

Disallow: /offices/europe/france/includes/

Disallow: /offices/europe/france/ibooks/

Disallow: /offices/europe/france/librairie/

Disallow: /offices/europe/france/analystes/

Disallow: /offices/europe/france/academic/pdf/

Disallow: /offices/europe/france/academic/xml/

Disallow: /offices/europe/france/academic/pdf/

Disallow: /offices/europe/france/sasforum/pdf/

Disallow: /offices/europe/france/sasforum/xml/

Disallow: /offices/europe/france/sasforum/js/

Disallow: /offices/europe/france/sasforum/modal/

Disallow: /offices/europe/france/sasforum/inc/

Disallow: /offices/europe/france/sasforum/fla/

Disallow: /offices/europe/france/sasforum/fancybox/

Disallow: /offices/europe/france/sasforum/css/

Disallow: /en_us/offers/sem/

Disallow: /*.modal.html$

Disallow: /etc/clientcontext/*

Disallow: */sandbox/

Disallow: */en_us/23289

Disallow: */en_us/admin/

Disallow: */En_us/events/test/

Disallow: */En_us/offers/test/

Disallow: */en_us/offers/test/

Disallow: */email/

Disallow: */en_xx/

Disallow: /ci360-content/

Disallow: /content/dam/SAS/partnernet/

Disallow: /content/sascom/de_de/partnernet/

Disallow: /content/sascom/de_de/partnernet-reseller/

Disallow: /content/sascom/ja_jp/partnernet/

Disallow: /content/sascom/ja_jp/partnernet-reseller/

Disallow: /de_de/partnernet/

Disallow: /de_de/partnernet-reseller/

Disallow: /en_us/partnernet/

Disallow: /fusionRedirect/

Disallow: /ja_jp/partnernet/

Disallow: /ja_jp/partnernet-reseller/

Disallow: /proudtobeageek/

Disallow: /profile/

Allow: /


User-agent: *

Disallow: /


Sitemap: https://www.hreflangxml.com/sas/sitemap-index.xml

Sitemap: https://www.hreflangxml.com/sas/hreflang-sitemap.xml

Sitemap: https://www.hreflangxml.com/sas/hreflang-primer-sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 37705 entries Valid XML No
Sample URLs:
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
2 redirect(s), 237 ms total
REVIEW
2 redirect(s), 237 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.sas.com/

https://sas.com

103 ms · HTTP/1.1

301

https://www.sas.com/

25 ms · HTTP/1.1

302

https://www.sas.com/en_us/home.geo.html

109 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://sas.com301103 msHTTP/1.1Apache
2https://www.sas.com/30225 msHTTP/1.1Apache
3https://www.sas.com/en_us/home.geo.html200109 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 54 ms lookup
PASS
1 A records, 54 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.173.160.3
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: extdns01.na.sas.com, extdns02.na.sas.com, extdns03.na.sas.com, extdns04.na.sas.com, extdns05.na.sas.com, extdns06.na.sas.com
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: 54 ms
Got: 54 ms
A149.173.160.3
AAAA—
CNAME—
NSextdns01.na.sas.com, extdns02.na.sas.com, extdns03.na.sas.com, extdns04.na.sas.com, extdns05.na.sas.com, extdns06.na.sas.com
MX
0 sas-com.mail.protection.outlook.com
TXT
TAILSCALE-xGh6ez1kXtFZHfR9n4yy
2e735e0e531a41c69412d9cb275e3703
_p8bhxv6bu8nygj2y9kpxs9codvtj499
asv=d6903657ebce2a62a24d9ec3bdbfa5fa
apple-domain-verification=25b1BtkpxgpBrD7e
docusign=9a58384d-dc45-43b2-bd6a-665ff08e269c
docusign=a049f97f-d635-48ff-9f33-baa6df4234dc
docker-verification=a70b17c2-aa1d-4fd5-82e1-09e9ffeebfcd
ms-domain-verification=071ec8e8-5667-4b2d-884e-7fb3947f37ef
ms-domain-verification=25bed1ae-59d5-490f-865e-5e150d16fd85
ms-domain-verification=7d9b5786-5704-4f39-b876-5806d9051d5e
ms-domain-verification=9568ff53-2039-4d41-8739-10ab0a7b6c1a
ms-domain-verification=b2bb2665-d90c-4075-8ab0-b21c0fcb0943
ms-domain-verification=b5223d8c-3b7c-45c5-9716-fcb202903e12
smartsheet-site-validation=aUV3HH-5nifm_U84HqNCvgfaM3CC_Os3
twilio-domain-verification=ddca8d4c9c57b5d3bb1ac276f34f49cd
anthropic-domain-verification-jkkhrz=3t3Y0cd5U7ACm12GKuKMv147P
pendo-domain-verification=404d45da-fdac-47f1-8ec2-ab64e0b38385
workplace-domain-verification=8e4d7e22-3169-4323-83d0-c6357ec88ed4
google-site-verification=1WdmN5YbJzRFp1SIF0rskESbz0MPdQbreaVFpJvBba8
google-site-verification=SanWThSK-VJmZSQi799rccahagseL8MHwQlGo59G4cE
google-site-verification=h_UHgixGKD_eBJV3V1P05ehaaDiimf79fk0m19SM2aU
h1-domain-verification=irCyLndGsMCVgSPwxQpxC6sxKkJJQhVrGgTa2UXAA5U4MVks
LA8qNOjO3BnjiVtmH1BSWzY9i24IGtGZErsZ+jxhIJP7bmP3zNzvLp8V25w4QW2s5shzW2TA1urbHsaJ...
Dynatrace-site-verification=1d6a2bc5-92f6-42fc-a244-c5808cde8662__mqts0gka9umu5m...
atlassian-domain-verification=GRomroaPE7T0Ket99nuYwdz7hBlqaD5ZvOUnLXbfxiKoWJD4yf...
paloaltonetworks-site-verification=2c88f593953572f90c9d024f73d9d6293f3e0614fff57...
SPF v=spf1 include:spf.protection.outlook.com ip4:192.31.37.0/24 ip4:192.31.22.0/24 ...
CAALookup not available with standard resolver
Resolved in 54 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+
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.sas.com/
200https://sas.com/

Preferred variant: non-www

HTTP → HTTPS

301http://sas.com/ → https://www.sas.com/

Consistent

A+
Domain Intelligence
sas.com — via Nom-iq Ltd. dba COM LAUDE, 36 years, 7 months old, hosted on SAS-WHQ - SAS Institute, Inc., US
PASS
sas.com — via Nom-iq Ltd. dba COM LAUDE, 36 years, 7 months old, hosted on SAS-WHQ - SAS Institute, Inc., US
Info::
Domain registered until Mar 3, 2027 (10 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Nom-iq Ltd. dba COM LAUDE
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: SAS-WHQ - SAS Institute, Inc., US
Got: AS12229
Domain expiry

227 days

March 3, 2027

SSL certificate

105 days

Issued by DigiCert Inc

Domain age

36 years, 7 months

Registered March 2, 1990

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

SAS-WHQ - SAS Institute, Inc., US

ASN AS12229

149.173.160.3

Registrar

Nom-iq Ltd. dba COM LAUDE

Unlocked 6 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 Nom-iq Ltd. dba COM LAUDE
Created March 2, 1990 (36 years, 7 months ago)
Expires March 3, 2027 (10 months)
Last Updated March 12, 2026
Name Servers extdns01.na.sas.com, extdns02.na.sas.com, extdns03.na.sas.com, extdns04.na.sas.com, extdns05.na.sas.com, extdns06.na.sas.com
DNSSEC Enabled
Hosting
IP Address 149.173.160.3
ASN AS12229 (SAS-WHQ - SAS Institute, Inc., US)
Provider SAS-WHQ - SAS Institute, Inc., US
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 12 ms TCP Connect 13 ms TLS Handshake 44 ms Server Processing 30 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