Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
#
# robots.txt for sfdc appservers.
#
# For use by salesforce.com
#
User-agent: googlebot
Allow: /
User-agent: * # applies to all robots
Allow: /?*un=*&pw=*
Allow: /?*pw=*&un=*
Allow: /secur/frontdoor.jsp?*sid=*
Allow: /secur/contentDoor?*sid=*
Allow: /secur/myDomainDoor?*sid=*
Allow: /secur/LoginInterstitial.apexp
Allow: /secur/login_portal.jsp?*pw=*
Allow: /sserv/login.jsp?*pw=*
Allow: /login.jsp?*pw=*
Allow: /login/login.jsp?*pw=*
Allow: /secur/login_page.jsp?*pw=*
Disallow: / # disallow indexing of all pages
No sitemap found
Adding a sitemap helps search engines discover your pages.
BTLS Certificate Expiry & Recommendations145 days until leaf cert expires — 2 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records3 A records, 11 ms lookupPASS
| A | 3.146.43.228, 3.146.43.227, 3.146.43.229 |
| AAAA | — |
| CNAME | — |
| NS | dns1.p06.nsone.net, dns2.p06.nsone.net, dns3.p06.nsone.net, dns4.p06.nsone.net, ns01.salesforce-dns.com, ns02.salesforce-dns.com, ns03.salesforce-dns.com, ns04.salesforce-dns.com |
| MX | — |
| TXT | 00do0000000bfdpeaq |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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'.
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)
A+Redirect ChainNo redirects — direct accessPASS
https://salesforce-sites.com
95 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://salesforce-sites.com | 200 | 95 ms | HTTP/1.1 | sfdcedge |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencesalesforce-sites.com — via MarkMonitor Inc., 7 years, 2 months old, hosted on AWSPASS
283 days
March 26, 2027
145 days
Issued by DigiCert Inc
7 years, 2 months
Registered March 26, 2019
Enabled
Protects against DNS spoofing
AWS
ASN AS14618
34.226.36.51
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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.
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