Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 602 ms totalFIX
https://familysearch.org
278 ms · HTTP/1.1
https://www.familysearch.org:443/
99 ms · HTTP/1.1
https://www.familysearch.org/en/home/
127 ms · HTTP/1.1
https://www.familysearch.org/en/united-s...
98 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://familysearch.org | 301 | 278 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.familysearch.org:443/ | 307 | 99 ms | HTTP/1.1 | Heroku |
| 3 | https://www.familysearch.org/en/home/ | 302 | 127 ms | HTTP/1.1 | Heroku |
| 4 | https://www.familysearch.org/en/united-s... | 200 | 98 ms | HTTP/1.1 | Heroku |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
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
BTLS Certificate Expiry & Recommendations63 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
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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, 71 ms lookupPASS
| A | 54.236.158.209, 54.198.138.249 |
| AAAA | — |
| CNAME | — |
| NS | ns-1481.awsdns-57.org, ns-1938.awsdns-50.co.uk, ns-285.awsdns-35.com, ns-757.awsdns-30.net |
| MX | 10 familysearch-org.mail.protection.outlook.com |
| TXT | 1rn6c9nh4619f7grv7nr8hyz4mty5qg5 Dynatrace-site-verification=01fe5b77-fca9-4449-ac01-bd46d84de1b9__uup9r4kddouuo7... MS=ms62285318 Validity-Domain-Verification=Jn4wYYH/SK3Ikm59OAvLY6qpYme= ZOOM_verify_lMC9_ljtQY2vqNUrobjHSw anthropic-domain-verification-gaafkh=VQPpeIqLDXKFKkZW1urw2pbsL atlassian-domain-verification=3Dqf1aq/7c1KdbsLIafbqX74I0vcW6pAbM0v6ocK8bw9/yvuWn... cisco-ci-domain-verification=5ab7b8e0f9d18911db10df28bc2e1b139c837cc7538703556f0... docker-verification=4b213244-5b9f-420b-8980-3ded5a4fe40a dropbox-domain-verification=e4s77r1l6tcc google-site-verification=6KKVYhlRvHTViW2RA7A5__ZXTikT7uAf03ePMNessFo google-site-verification=Oshp3Lx_xob63dlDgFOHCXmtS1OVftgM3cdKjWZ3Hlc openai-domain-verification=dv-OTE6I3HmNfgihqGQHdzBzg3I traction-guest=b60a6d25-4e72-413e-87e1-d2da15f38c18 SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all |
| 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.
A+Crawlabilityrobots.txt present, sitemap with 110 URLsPASS
User-agent: *
Disallow: /ark:/61903/1:
Disallow: /ark:/61903/2:
Disallow: /auth/
Disallow: /campaign
Disallow: /*/campaign
Disallow: /frontier/
Disallow: /identity/
Disallow: /*/identity/
Disallow: /learningcenter
Disallow: /mgmt/
Disallow: /pal:/
Disallow: /photos/album/
Disallow: /photos/person/
Disallow: /photos/view/
Disallow: /profile/
Disallow: /records/pal:/
Disallow: /recover/
Disallow: /*/recover/
Disallow: /register/
Disallow: /*/register/
Disallow: /Search/
Disallow: /service/temple/cards
Disallow: /tree
Allow: /tree/
Disallow: /tree/contributions
Disallow: /tree/find
Disallow: /tree/following
Disallow: /tree/import
Disallow: /tree/improve-place-names
Disallow: /tree/pedigree
Disallow: /tree/person
Disallow: /tree/sources
Disallow: /search/all-collections/results/
Disallow: *?icid=
Disallow: *?cid=
Disallow: /*?00
Disallow: /*?ref=*
Disallow: /*genealogies/submission*
Disallow: /*/home/portal/
Disallow: /*/search/catalog/results
# Home Pages Experiment
Sitemap: https://www.familysearch.org/sitemap-home-pages-experiment.xml
# Sitemap: https://www.familysearch.org/sitemap-index-home-page.xml
# Census Records Experiment
Sitemap: https://www.familysearch.org/sitemap-index-census-experiment.xml
# Memories
Sitemap: https://www.familysearch.org/photos/sitemapIndex?category=artifacts&artifactCategory=IMAGE
Sitemap: https://www.familysearch.org/photos/sitemapIndex?category=artifacts&artifactCategory=TEXT
# Allow Algolia to search /frontier
User-agent: Algolia Crawler
Allow: /frontier
# Allow social share previews of campaigns
User-agent: facebookexternalhit
Allow: /campaign/
Allow: /*/campaign/
User-agent: Twitterbot
Allow: /campaign/
Allow: /*/campaign/
## Specific rules for familysearch wiki (familysearch.org/<lang>/wiki/...)
# advertising-related bots:
User-agent: Mediapartners-Google*
Disallow: /*/wiki/
# Friendly, low-speed bots are welcome viewing article pages, but not
# dynamically-generated pages please.
#
# Inktomi's "Slurp" can read a minimum delay between hits; if your
# bot supports such a thing using the 'Crawl-delay' or another
# instruction, please let us know.
#
# There is a special exception for API mobileview to allow dynamic
# mobile web & app views to load section content.
# These views aren't HTTP-cached but use parser cache aggressively
# and don't expose special: pages etc.
#
# Another exception is for REST API documentation, located at
# /api/rest_v1/?doc.
#
User-agent: *
Allow: /*/wiki/w/api.php?action=mobileview&
Allow: /*/wiki/w/load.php?
Allow: /*/wiki/api/rest_v1/?doc
# Disallow indexing of non-article content
Disallow: /*/wiki/w/
Disallow: /*/wiki/api/
Disallow: /*/wiki/trap/
Disallow: /*/wiki/Special:*
Disallow: /*/wiki/index.php?
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
ADomain Intelligencefamilysearch.org — via Key-Systems GmbH, 28 years, 2 months old, hosted on AWSPASS
EXPIRED
June 24, 2026
63 days
Issued by DigiCert Inc
28 years, 2 months
Registered June 25, 1998
Not enabled
Protects against DNS spoofing
AWS
ASN AS14618
54.236.158.209
Key-Systems GmbH
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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