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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations192 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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 Records2 A records, 29 ms lookupPASS
| A | 44.209.206.23, 52.4.55.98 |
| AAAA | — |
| CNAME | — |
| NS | ns-1484.awsdns-57.org, ns-372.awsdns-46.com, ns-1008.awsdns-62.net, ns-1803.awsdns-33.co.uk |
| MX | 10 guidestar-org.mail.protection.outlook.com |
| TXT | globalsign-domain-verification=4C91062FCFE1413B492838C455A8F4CA ms=ms89461254 AGQI2qR0IczgUeJbIJZMFS1bxxTbtcqm+R6w2B53Q+DSE7zYshzrObL71xHls4GpZJgKQ8EDc6Z292Zx... google-site-verification=q-4eQCrROiMeSk2dPlcjubnpmqCTVStzkXE8PFm0OOg SPF v=spf1 include:spf.protection.outlook.com a mx include:spf.braintreegateway.com ... |
| 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.
ARedirect Chain1 redirect(s), 928 ms totalPASS
https://guidestar.org
383 ms · HTTP/1.1
https://www.guidestar.org/
545 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://guidestar.org | 301 | 383 ms | HTTP/1.1 | Microsoft-IIS/10.0 |
| 2 | https://www.guidestar.org/ | 200 | 545 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
ACrawlabilityrobots.txt present, no sitemapPASS
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
User-agent: *
Disallow: *.axd$
Disallow: /bin
Disallow: /config
Disallow: /CuteSoft_Client
Disallow: /js
Disallow: /onlineopinionF3cS
Disallow: /onlineopinionV5
Disallow: /xsl
Disallow: /PartnerSearch.aspx
Disallow: /PartnerDocuments.aspx
Disallow: /UserData.aspx
Disallow: /BrowserSearch.xml
Disallow: /FinDocuments
Disallow: /popup_salesforce.html
Disallow: /ViewPDF.aspx
Disallow: /Profile/ViewPdf
Disallow: /Error/DistilBlock
Disallow: /Account/Register
Disallow: /organizations
User-agent: Ezooms
Disallow: /
User-agent: percbotspider
Disallow: /
User-agent: facebookexternalhit
Disallow: /rxg/
Disallow: /rxa/
User-agent: 008
Disallow: /
User-Agent: WellKnownBot
Disallow: /
Sitemap: https://www.guidestar.org/sitemapIndex.xml
No sitemap found
Adding a sitemap helps search engines discover your pages.
A+Domain Intelligenceguidestar.org — via Amazon Registrar, Inc., 30 years, 5 months old, hosted on AWSPASS
308 days
April 20, 2027
192 days
Issued by Sectigo Limited
30 years, 5 months
Registered April 19, 1996
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
44.209.206.23
Amazon Registrar, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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