Skip to content
https://www.salesforce.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
6
PASS
3
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
3 PASS 6 REVIEW
B
DNS Records
2 A records, 30 ms lookup
REVIEW
2 A records, 30 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.110.240.152, 104.110.240.163
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:b200::58dd:1983, 2a02:26f0:b200::58dd:1978
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.salesforce.com.edgekey.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 30 ms
Got: 30 ms
A104.110.240.152, 104.110.240.163
AAAA2a02:26f0:b200::58dd:1983, 2a02:26f0:b200::58dd:1978
CNAMEwww.salesforce.com.edgekey.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 30 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
Redirect Chain
2 redirect(s), 170 ms total
REVIEW
2 redirect(s), 170 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.salesforce.com

https://www.salesforce.com

50 ms · HTTP/1.1

302

https://www.salesforce.com/nl/?ir=1

20 ms · HTTP/1.1

302

https://www.salesforce.com/nl/?ir=1&bc=D...

100 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.salesforce.com30250 msHTTP/1.1AkamaiGHost
2https://www.salesforce.com/nl/?ir=130220 msHTTP/1.1AkamaiGHost
3https://www.salesforce.com/nl/?ir=1&bc=D...200100 msHTTP/1.1

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

B
Crawlability
robots.txt present, sitemap with 948 URLs
REVIEW
robots.txt present, sitemap with 948 URLs
Info::
robots.txt is present
Got: 10240 bytes
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 948 entries
Info::
robots.txt references sitemap

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 10240 B Sitemaps referenced 51 User-agents *, AdsBot-Google, MS Search 4.0 Robot, Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 4.0 Robot), Mozilla/4.0 (compatible; MSIE 6.0; Windows NT; MS Search 4.0 Robot), Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 5.0 Robot), Mozilla/4.0 (compatible; MSIE 6.0; Windows NT; MS Search 5.0 Robot) Blocking No — crawling allowed
# Robots.txt file for http://www.salesforce.com
# All robots will spider the domain
#
Sitemap: https://www.salesforce.com/sitemap.xml
Sitemap: https://www.salesforce.com/ap/sitemap.xml
Sitemap: https://www.salesforce.com/au/sitemap.xml
Sitemap: https://www.salesforce.com/br/sitemap.xml
Sitemap: https://www.salesforce.com/ca/sitemap.xml
Sitemap: https://www.salesforce.com/cn/sitemap.xml
Sitemap: https://www.salesforce.com/de/sitemap.xml
Sitemap: https://www.salesforce.com/dk/sitemap.xml
Sitemap: https://www.salesforce.com/es/sitemap.xml
Sitemap: https://www.salesforce.com/fi/sitemap.xml
Sitemap: https://www.salesforce.com/fr/sitemap.xml
Sitemap: https://www.salesforce.com/fr-ca/sitemap.xml
Sitemap: https://www.salesforce.com/in/sitemap.xml
Sitemap: https://www.salesforce.com/it/sitemap.xml
Sitemap: https://www.salesforce.com/jp/sitemap.xml
Sitemap: https://www.salesforce.com/kr/sitemap.xml
Sitemap: https://www.salesforce.com/mx/sitemap.xml
Sitemap: https://www.salesforce.com/nl/sitemap.xml
Sitemap: https://www.salesforce.com/no/sitemap.xml
Sitemap: https://www.salesforce.com/se/sitemap.xml
Sitemap: https://www.salesforce.com/th/sitemap.xml
Sitemap: https://www.salesforce.com/tw/sitemap.xml
Sitemap: https://www.salesforce.com/uk/sitemap.xml
Sitemap: https://www.salesforce.com/eu/sitemap.xml
Sitemap: https://www.salesforce.com/sa/sitemap.xml
Sitemap: https://www.salesforce.com/blog/sitemap_index.xml
Sitemap: https://www.salesforce.com/au/blog/sitemap_index.xml
Sitemap: https://www.salesforce.com/br/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/ca/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/de/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/es/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/fi/blog/sitemap.xml
Sitemap: https://www.salesforce.com/fr/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/it/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/jp/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/mx/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/nl/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/eu/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/sitemap-forms.xml
Sitemap: https://www.salesforce.com/plus-sitemap.xml
Sitemap: https://www.salesforce.com/plus/api/sitemap.xml
Sitemap: https://www.salesforce.com/nl/blog/sitemap_index.xml
Sitemap: https://www.salesforce.com/sitemap-events.xml
Sitemap: https://www.salesforce.com/au/blog/sf_topic-sitemap.xml
Sitemap: https://www.salesforce.com/au/blog/page-sitemap.xml
Sitemap: https://www.salesforce.com/au/blog/post-sitemap.xml
Sitemap: https://www.salesforce.com/uk/news/sitemap_index.xml
Sitemap: https://www.salesforce.com/news/page-sitemap.xml
Sitemap: https://www.salesforce.com/news/post-sitemap.xml
Sitemap: https://www.salesforce.com/news/sitemap_index.xml
Sitemap: https://www.salesforce.com/in/blog/post-sitemap.xml

# Keep mis-configured Microsoft SharePoint servers from hammering us
# This is not MSN Search (msnbot), but privately owned SharePoint installations
User-agent: MS Search 4.0 Robot
Disallow: /

User-agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 4.0 Robot)
Disallow: /

User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT; MS Search 4.0 Robot)
Disallow: /

User-agent: Mozilla/4.0 (compatible; MSIE 4.01; Windows NT; MS Search 5.0 Robot)
Disallow: /

User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT; MS Search 5.0 Robot)
Disallow: /

User-agent: *
Disallow: /products/home-perf/
Disallow: /form/conf/
Disallow: */conf/
Disallow: /content/dam/web/en_us/www/documents/
Disallow: /content/dam/web/en_us/www/assets/pdf/
Disallow: /login-messages/
Disallow: /au/login-messages/
Disallow: /ap/login-messages/
Disallow: /in/login-messages/
Disallow: /cn/login-messages/
Disallow: /tw/login-messages/
Disallow: /th/login-messages/
Disallow: /uk/login-messages/
Disallow: /de/login-messages/
Disallow: /ca/login-messages/
Disallow: /eu/login-messages/
Disallow: /fr/login-messages/
Disallow: /es/login-messages/
Disallow: /it/login-messages/
Disallow: /nl/login-messages/
Disallow: /fi/login-messages/
Disallow: /dk/login-messages/
Disallow: /se/login-messages/
Disallow: /fr-ca/login-messages/
Disallow: /competitive/gated-content-for-agents/
Allow: /plus/experience/*/series/
Disallow: /plus/experience/*/
Disallow: /plus/experience/dreamforce_2025_x_test

#Disallow DAMs
Disallow: /content/dam/web/pt_br/www/
Disallow: /content/dam/web/es_mx/www/
Disallow: /content/dam/web/de_de/www/
Disallow: /content/dam/web/fr_fr/www/
Disallow: /content/dam/web/nl_nl/www/
Disallow: /content/dam/web/es_es/www/
Disallow: /content/dam/web/it_it/www/
Disallow: /content/dam/web/sv_se/www/
Disallow: /content/dam/web/fr_ca/www/
Disallow: /content/dam/web/fi_fi/www/
Disallow: /content/dam/web/da_dk/www/
Disallow: /content/dam/web/en_is/www/
Disallow: /content/dam/web/en_gb/www/
Disallow: /content/dam/web/en_ie/www/
Disallow: /content/dam/web/en_ca/www/
Disallow: /content/dam/web/en_dk/www/
Disallow: /content/dam/web/no_no/www/
Disallow: /content/dam/web/de_ch/www/
Disallow: /content/dam/web/fr_ch/www/
Disallow: /content/dam/web/it_ch/www/
Disallow: /content/dam/web/en_au/www/
Disallow: /content/dam/web/en_sg/www/
Disallow: /opencms/
Disallow: /promos/
Disallow: /styleguide/
Disallow: /landing/
Disallow: /modules/
Disallow: /uk/promos/
Disallow: /eu/promos/
Disallow: /de/promos/
Disallow: /es/promos/
Disallow: /fr/promos/
Disallow: /it/promos/
Disallow: /jp/promos/

# Company pages duped across locales
Disallow: /us/developer/docs/ajaxpre
Disallow: /us/developer/docs/ajax80
Disallow: /us/developer/docs/ajax90
Disallow: /us/developer/docs/ajax1*
Disallow: /us/developer/docs/ajax2*
Disallow: /us/developer/docs/ajax3*
Disallow: /us/developer/docs/ajax4*
Disallow: /us/developer/docs/apexcodepre
Disallow: /us/developer/docs/apexcode1*
Disallow: /us/developer/docs/apexcode2*
Disallow: /us/developer/docs/apexcode3*
Disallow: /us/developer/docs/apexcode4*
Disallow: /us/developer/docs/api_asynchpre
Disallow: /us/developer/docs/api_asynch1*
Disallow: /us/developer/docs/api_asynch2*
Disallow: /us/developer/docs/api_asynch3*
Disallow: /us/developer/docs/api_asynch4*
Disallow: /us/developer/docs/api_consolepre
Disallow: /us/developer/docs/api_console2*
Disallow: /us/developer/docs/api_console3*
Disallow: /us/developer/docs/api_console4*
Disallow: /us/developer/docs/api_metapre
Disallow: /us/developer/docs/api_meta1*
Disallow: /us/developer/docs/api_meta2*
Disallow: /us/developer/docs/api_meta3*
Disallow: /us/developer/docs/api_meta4*
Disallow: /us/developer/docs/api_restpre
Disallow: /us/developer/docs/api_rest2*
Disallow: /us/developer/docs/api_rest3*
Disallow: /us/developer/docs/api_rest4*
Disallow: /us/developer/docs/api_streamingpre
Disallow: /us/developer/docs/api_streaming2*
Disallow: /us/developer/docs/api_streaming3*
Disallow: /us/developer/docs/api_streaming4*
Disallow: /us/developer/docs/apipre
Disallow: /us/developer/docs/api80
Disallow: /us/developer/docs/api90
Disallow: /us/developer/docs/api1*
Disallow: /us/developer/docs/api2*
Disallow: /us/developer/docs/api3*
Disallow: /us/developer/docs/api4*
Disallow: /us/developer/docs/chatterapipre
Disallow: /us/developer/docs/chatterapi2*
Disallow: /us/developer/docs/chatterapi3*
Disallow: /us/developer/docs/chatterapi4*
Disallow: /us/developer/docs/dbcom_apipre
Disallow: /us/developer/docs/dbcom_api2*
Disallow: /us/developer/docs/dbcom_api3*
Disallow: /us/developer/docs/dbcom_api4*
Disallow: /us/developer/docs/dbcom_objectspre
Disallow: /us/developer/docs/dbcom_objects2*
Disallow: /us/developer/docs/dbcom_objects3*
Disallow: /us/developer/docs/dbcom_objects4*
Disallow: /us/developer/docs/dbcom_soql_soslpre
Disallow: /us/developer/docs/dbcom_soql_sosl2*
Disallow: /us/developer/docs/dbcom_soql_sosl3*
Disallow: /us/developer/docs/dbcom_soql_sosl4*
Disallow: /us/developer/docs/daaspre
Disallow: /us/developer/docs/daas140
Disallow: /us/developer/docs/fundamentalspre
Disallow: /us/developer/docs/knowledge_devpre
Disallow: /us/developer/docs/object_referencepre
Disallow: /us/developer/docs/object_reference2*
Disallow: /us/developer/docs/object_reference3*
Disallow: /us/developer/docs/object_reference4*
Disallow: /us/developer/docs/officetoolkit30
Disallow: /us/developer/docs/pagespre
Disallow: /us/developer/docs/pages1*
Disallow: /us/developer/docs/pages2*
Disallow: /us/developer/docs/pages3*
Disallow: /us/developer/docs/pages4*
Disallow: /us/developer/docs/sforce20
Disallow: /us/developer/docs/sforce30
Disallow: /us/developer/docs/sforce40
Disallow: /us/developer/docs/sforce50
Disallow: /us/developer/docs/sforce60
Disallow: /us/developer/docs/sforce70


Disallow: /search.jsp
Disallow: /assets/pdf/company/private/
Disallow: /jp/assets/pdf/
Disallow: /content/dam/web/ja_jp/www/documents/ 
Disallow: /content/dam/web/ja_jp/www/assets/pdf/
Disallow: /content/blogs/au/en/*
Disallow: /content/blogs/us/en/*
Disallow: /content/blogs/nl/nl/*
Disallow: /content/blogs/eu/en/*
Disallow: /content/blogs/in/en/*
Disallow: /content/blogs/fi/fi/*
Disallow: /content/blogs/sg/en/*
Disallow: /content/blogs/jp/ja/*
Disallow: /content/blogs/mx/es/*
Disallow: /content/blogs/es/es/*
Disallow: /content/blogs/br/pt/*
Disallow: /content/blogs/il/he/*
Disallow: /content/blogs/it/it/*

User-agent: AdsBot-Google
Allow: /
Disallow: /de/assets/
Disallow: /fr/assets/
Disallow: /se/assets/
Disallow: /es/assets/
Disallow: /it/assets/
Disallow: /nl/assets/
Disallow: /uk/assets/
Disallow: /eu/assets/
Disallow: /content/dam/web/en_us/www/documents/legal/misc/456456.pdf
Disallow: /content/dam/web/en_us/www/documents/legal/misc/usla-excluded-services.pdf
Disallow: /content/dam/web/en_us/www/documents/legal/supplier/salesforce-vendor-privacy-exhibit-emea_psa_subcontractors-archived-121118.pdf
Disallow: /content/dam/web/en_us/www/documents/legal/Agreements/product-specific-terms/premier-priority-terms.pdf
Disallow: /dig-perf-test/
Disallow: /content/dam/web/en_us/www/documents/legal/no-index/
Disallow: /content/dam/web/en_us/www/documents/legal/work-unit-catalog/

# STARTS
# Block crawl of ._filter.alphaSort which is duplicate of /customer-success-stories/
# Note the $ delimiter so that this doesnt impact other 
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 403 Expected: 301 redirect to HTTPS

www / non-www

200https://www.salesforce.com/
301https://salesforce.com/

Preferred variant: www

HTTP → HTTPS

403http://www.salesforce.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:b200::58dd:1983, 2a02:26f0:b200::58dd:1978
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:b200::58dd:1983, 2a02:26f0:b200::58dd:1978 Connection Reachable (1 ms)
A+
Domain Intelligence
salesforce.com — via MarkMonitor Inc., 27 years, 8 months old, hosted on Akamai
PASS
salesforce.com — via MarkMonitor Inc., 27 years, 8 months old, hosted on Akamai
Info::
Domain registered until Oct 21, 2026 (6 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: MarkMonitor Inc.
Info::
Hosting: Akamai
Got: AS33905
Domain expiry

65 days

October 21, 2026

SSL certificate

181 days

Issued by DigiCert Inc

Domain age

27 years, 8 months

Registered December 2, 1998

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Akamai

ASN AS33905

23.1.106.133

Registrar

MarkMonitor Inc.

Lock status unknown 6 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
Registrar MarkMonitor Inc.
Created December 2, 1998 (27 years, 8 months ago)
Expires October 21, 2026 (6 months)
Last Updated September 19, 2024
Name Servers pch1.salesforce-dns.com, pch2.salesforce-dns.com, udns1.salesforce.com, udns2.salesforce.com, udns3.salesforce.com, udns4.salesforce.com
DNSSEC Enabled
Hosting
IP Address 23.1.106.133
ASN AS33905 (AKAMAI-AMS, NL)
Provider Akamai
Data source: rdap (0.6s)
A+
HTTP Probe Timing
Total 64 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
16 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
64 ms
Total Time Total request time from DNS lookup through full response.
64 ms

Connection waterfall

DNS Lookup 16 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 40 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