Skip to content
https://idealist.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
B
Redirect Chain
2 redirect(s), 387 ms total
REVIEW
2 redirect(s), 387 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.idealist.org/

https://idealist.org

16 ms · HTTP/1.1

301

https://www.idealist.org/

99 ms · HTTP/1.1

302

https://www.idealist.org/en

272 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://idealist.org30116 msHTTP/1.1Varnish
2https://www.idealist.org/30299 msHTTP/1.1Heroku
3https://www.idealist.org/en200272 msHTTP/1.1Heroku

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

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
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

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 Records
4 A records, 8 ms lookup
PASS
4 A records, 8 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.2.49, 151.101.130.49, 151.101.66.49, 151.101.194.49
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns14.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns15.dnsmadeeasy.com
Info::
7 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 8 ms
Got: 8 ms
A151.101.2.49, 151.101.130.49, 151.101.66.49, 151.101.194.49
AAAA—
CNAME—
NSns14.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns10.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns15.dnsmadeeasy.com
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx3.googlemail.com
30 aspmx5.googlemail.com
30 aspmx2.googlemail.com
30 aspmx4.googlemail.com
TXT
google-site-verification=Qss67lf6CEtTEKuQOgSqYAyn0P5pwNnolmuOc176OqU
google-site-verification=YxzOU9owbOLy2xLAwxAQZr1zEFzO--8kZvfkvr9yBOk
facebook-domain-verification=dxnlu4my4wgiabo1l2awpc4ghxp1dr
_globalsign-domain-verification=OrpPCKxSUyu45DqtvM0ZrlPwjsZdP1BIYj1U7PyF3y
SPF v=spf1 include:cust-spf.exacttarget.com include:_spf.google.com include:aspmx.pa...
google-site-verification=prBoZIfon5IPCB5ig6sdU17ARh6tLikyD2NRrZ4jE-M
google-site-verification=QqYK1t_ox2ORHUuQjHQ7FnqFJvZRCqWb0QsA1iNPFDc
_globalsign-domain-verification=O60kZMoa5mBPIKKqd9FSRXcGUhU6s3rzZHzWNLAlL7
google-site-verification=DvZjnrn_0ddZEsp48TUr08IzyBrBBi8vYda83k_JB9w
google-site-verification=hA2wDZOxAgz1WQRK9D6B4rEA8Q4kjlr-k8Cn7w7PWwE
google-site-verification=v5rxIxfih6q8A6U7503x3wPngDlOT7wwOA2U7qtGGhc
pardot_324951_*=e7228734c7524a408efb26601d65e4bdf6f95981c34f2bbf53d5c9d8f6fd6883
CAALookup not available with standard resolver
Resolved in 8 ms

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.

A+
Crawlability
robots.txt present, sitemap with 95 URLs
PASS
robots.txt present, sitemap with 95 URLs
Info::
robots.txt is present
Got: 153 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 95 entries
Info::
Sitemap index with 95 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 153 B Sitemaps referenced 1 User-agents *, Google-Extended Blocking No — crawling allowed
User-agent: *
Disallow: */third-party-login?provider=*

User-agent: Google-Extended
Disallow: /en/careers/

Sitemap: https://www.idealist.org/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 95 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.idealist.org/
200https://idealist.org/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
idealist.org — via Gandi SAS, 30 years, 1 months old, hosted on Fastly
PASS
idealist.org — via Gandi SAS, 30 years, 1 months old, hosted on Fastly
Info::
Domain registered until Aug 21, 2026 (4 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: Gandi SAS
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: Fastly
Got: AS54113
Domain expiry

66 days

August 21, 2026

SSL certificate

88 days

Issued by Let's Encrypt

Domain age

30 years, 1 months

Registered August 22, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.66.49

Registrar

Gandi SAS

Unlocked 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
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Gandi SAS
Created August 22, 1996 (30 years, 1 months ago)
Expires August 21, 2026 (4 months)
Last Updated May 30, 2025
Name Servers ns10.dnsmadeeasy.com, ns11.dnsmadeeasy.com, ns12.dnsmadeeasy.com, ns13.dnsmadeeasy.com, ns14.dnsmadeeasy.com, ns15.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 151.101.66.49
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.2s)

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 17 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 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.
17 ms
Total Time Total request time from DNS lookup through full response.
18 ms

Connection waterfall

DNS Lookup 7 ms TCP Connect 2 ms TLS Handshake 6 ms Server Processing 2 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT)
PASS
Fastly (HIT)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-sjc1000094-SJC
Info::
CDN cache status: HIT
CDN Detected: Fastly
Provider Fastly Cache Status HIT Evidence x-served-by: cache-sjc1000094-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback