Skip to content
https://immanuelfellowshipstl.org

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
8
PASS
9
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
9 PASS 8 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 198.49.23.144: lookup 198.49.23.144: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 198.185.159.144: lookup 198.185.159.144: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 198.49.23.145: lookup 198.49.23.145: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 198.185.159.145: lookup 198.185.159.145: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
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
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.immanuelfellowshipstl.org/
200https://immanuelfellowshipstl.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://immanuelfellowshipstl.org/ → https://www.immanuelfellowshipstl.org/

Consistent

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

Certificate validity

72
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 DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
C
CDN & Delivery
Action
Assets on Fastly (host assets.squarespace.com, 13 assets); document served directly from origin
REVIEW
Assets on Fastly (host assets.squarespace.com, 13 assets); document served directly from origin
Warning::
Document not behind existing CDN (Fastly serves the assets)
The page's subresources are delivered by Fastly (assets.squarespace.com, 13 assets), but the HTML document itself comes straight from the origin. Routing the document through the CDN already in use is the cheapest latency win available here -- the provider relationship, the certificate and the config already exist. A short edge TTL with stale-while-revalidate suits HTML that changes often; if the response is genuinely per-user, edge TLS termination alone still removes a full round trip from every visitor's first byte.
Got: delegation static.squarespace.map.fastly.net
Info::
Assets on Fastly: assets.squarespace.com (assets: 13), cache HIT, HIT
Got: delegation static.squarespace.map.fastly.net
Info::
Assets on Akamai: images.squarespace-cdn.com (assets: 7)
Got: delegation images.squarespace-cdn.com-v1.edgekey.net
Info::
Assets on Fastly: static1.squarespace.com (assets: 7), cache HIT, HIT
Got: delegation prod.squarespace.map.fastly.net
Warning: Assets on a CDN, document is not: Fastly
Document origin not attributed

Asset hosts on a CDN

  • assets.squarespace.com — Fastly · assets: 13 · Cache Status: HIT, HIT
  • images.squarespace-cdn.com — Akamai · assets: 7
  • static1.squarespace.com — Fastly · assets: 7 · Cache Status: HIT, HIT

Other asset hosts

  • definitions.sqspcdn.com — assets: 16 · not attributed
  • www.googletagmanager.com — assets: 1 · below probe threshold

The heavy static files already ride an edge network, but every visitor still waits on the origin for the HTML itself. Routing the document through the same CDN is usually a config change rather than a migration: a short edge TTL with stale-while-revalidate for cacheable HTML, or edge TLS termination alone when the response is per-user.

B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
A+
DNS Records
4 A records, 35 ms lookup
PASS
4 A records, 35 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 198.49.23.144, 198.185.159.144, 198.49.23.145, 198.185.159.145
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: ns03.squarespacedns.com, dns1.p01.nsone.net, dns4.p01.nsone.net, ns02.squarespacedns.com, dns3.p01.nsone.net, dns2.p01.nsone.net, ns01.squarespacedns.com, ns04.squarespacedns.com
Info::
5 mail exchanger(s) configured
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: 35 ms
Got: 35 ms
A198.49.23.144, 198.185.159.144, 198.49.23.145, 198.185.159.145
AAAA—
CNAME—
NSns03.squarespacedns.com, dns1.p01.nsone.net, dns4.p01.nsone.net, ns02.squarespacedns.com, dns3.p01.nsone.net, dns2.p01.nsone.net, ns01.squarespacedns.com, ns04.squarespacedns.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
google-site-verification=ZdFV9b4F9xiLZKqHV8sZh32Xmu3o74fw629mmWFT_Xo
CAALookup not available with standard resolver
Resolved in 35 ms

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 24ms across 3 resolvers (spread 5ms)
PASS
Mean 24ms across 3 resolvers (spread 5ms)
Info::
Cloudflare: 22ms
Got: 22ms via 1.1.1.1:53
Info::
Quad9: 24ms
Got: 24ms via 9.9.9.9:53
Info::
Google: 27ms
Got: 27ms via 8.8.8.8:53
A
Redirect Chain
1 redirect(s), 205 ms total
PASS
1 redirect(s), 205 ms total
Info::
Single redirect
Got: https://immanuelfellowshipstl.org → https://www.immanuelfellowshipstl.org/ (301)
Info::
WWW normalization redirect

https://immanuelfellowshipstl.org

110 ms · HTTP/1.1

301

https://www.immanuelfellowshipstl.org/

95 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://immanuelfellowshipstl.org301110 msHTTP/1.1Squarespace
2https://www.immanuelfellowshipstl.org/20095 msHTTP/1.1Squarespace

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 577 URLs
PASS
robots.txt present, sitemap with 577 URLs
Info::
robots.txt is present
Got: 1520 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 577 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1520 B Sitemaps referenced 1 User-agents TikTokSpider, YouBot, Ai2Bot-Dolma, MyCentralAIScraperBot, AdsBot-Google-Mobile-Apps, AI2Bot, GoogleOther, GoogleOther-Video, img2dataset, omgili, *, anthropic-ai, cohere-training-data-crawler, omgilibot, AdsBot-Google-Mobile, Applebot-Extended, CCBot, aiHitBot, cohere-ai, DuckAssistBot, Google-Extended, GPTBot, Quora-Bot, Amazonbot, ClaudeBot, GoogleOther-Image, AdsBot-Google, Bytespider, Meta-ExternalAgent, FacebookBot Blocking No — crawling allowed
# Squarespace Robots Txt

User-agent: AI2Bot
User-agent: Ai2Bot-Dolma
User-agent: aiHitBot
User-agent: Amazonbot
User-agent: anthropic-ai
User-agent: Applebot-Extended
User-agent: Bytespider
User-agent: CCBot
User-agent: ClaudeBot
User-agent: cohere-ai
User-agent: cohere-training-data-crawler
User-agent: DuckAssistBot
User-agent: FacebookBot
User-agent: Google-Extended
User-agent: GoogleOther
User-agent: GoogleOther-Image
User-agent: GoogleOther-Video
User-agent: GPTBot
User-agent: img2dataset
User-agent: Meta-ExternalAgent
User-agent: MyCentralAIScraperBot
User-agent: omgili
User-agent: omgilibot
User-agent: Quora-Bot
User-agent: TikTokSpider
User-agent: YouBot
User-agent: AdsBot-Google
User-agent: AdsBot-Google-Mobile
User-agent: AdsBot-Google-Mobile-Apps
User-agent: *
Disallow: /config
Disallow: /search
Disallow: /account$
Disallow: /account/
Disallow: /commerce/digital-download/
Disallow: /api/
Allow: /api/ui-extensions/
Disallow: /static/
Disallow:/*?author=*
Disallow:/*&author=*
Disallow:/*?tag=*
Disallow:/*&tag=*
Disallow:/*?month=*
Disallow:/*&month=*
Disallow:/*?view=*
Disallow:/*&view=*
Disallow:/*?format=json
Disallow:/*&format=json
Disallow:/*?format=page-context
Disallow:/*&format=page-context
Disallow:/*?format=main-content
Disallow:/*&format=main-content
Disallow:/*?format=json-pretty
Disallow:/*&format=json-pretty
Disallow:/*?format=ical
Disallow:/*&format=ical
Disallow:/*?reversePaginate=*
Disallow:/*&reversePaginate=*

Sitemap: https://www.immanuelfellowshipstl.org/sitemap.xml

A+
Domain Intelligence
immanuelfellowshipstl.org — via Tucows Domains Inc., 5 years, 1 months old, hosted on Squarespace
PASS
immanuelfellowshipstl.org — via Tucows Domains Inc., 5 years, 1 months old, hosted on Squarespace
Info::
Domain registered until Oct 18, 2027 (11 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Tucows Domains Inc.
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: Squarespace
Got: AS53831
Domain expiry

330 days

October 18, 2027

SSL certificate

72 days

Issued by Let's Encrypt

Domain age

5 years, 1 months

Registered October 18, 2021

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Squarespace

ASN AS53831

198.49.23.144

Registrar

Tucows Domains Inc.

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created October 18, 2021 (5 years, 1 months ago)
Expires October 18, 2027 (11 months)
Last Updated October 9, 2026
Name Servers dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net, ns01.squarespacedns.com, ns02.squarespacedns.com, ns03.squarespacedns.com, ns04.squarespacedns.com
DNSSEC Not enabled
Hosting
IP Address 198.49.23.144
ASN AS53831 (SQUARESPACE - Squarespace, Inc., US)
Provider Squarespace
Data source: rdap (0.6s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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

Connection waterfall

DNS Lookup 36 ms TCP Connect 32 ms TLS Handshake 38 ms Server Processing 39 ms Content Transfer 0 ms
A+
CDN Cache Observability
Cache state: Age=10307s
PASS
Cache state: Age=10307s
Info::
CDN cache state observable via 1 header(s)
Got: age=10307
A+
Health Check Endpoint
Health endpoint at https://immanuelfellowshipstl.org/healthz (HTTP 200)
PASS
Health endpoint at https://immanuelfellowshipstl.org/healthz (HTTP 200)
Info::
Public health endpoint at https://immanuelfellowshipstl.org/healthz
Got: https://immanuelfellowshipstl.org/healthz
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback