Skip to content
https://www.ecosia.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 3 REVIEW
B
DNS Records
2 A records, 63 ms lookup
REVIEW
2 A records, 63 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.64.150.71, 104.18.37.185
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3105::ac40:9647, 2a06:98c1:310d::6812:25b9
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.ecosia.org.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
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: 63 ms
Got: 63 ms
A172.64.150.71, 104.18.37.185
AAAA2a06:98c1:3105::ac40:9647, 2a06:98c1:310d::6812:25b9
CNAMEwww.ecosia.org.cdn.cloudflare.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 63 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

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)

C
Crawlability
Action
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 518 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 518 B Sitemaps referenced 0 User-agents *, ia_archiver, Twitterbot Blocking No — crawling allowed
User-agent: *
Disallow: /search
Disallow: /videos
Disallow: /images
Disallow: /install
Disallow: /news
Disallow: /map
Disallow: /maps
Disallow: /google
Disallow: /settings
Disallow: /firstrun
Disallow: /uninstall
Disallow: /account/*
Disallow: /accounts
Disallow: /accounts/*
Disallow: /shopping
Disallow: /chat
Disallow: /browser/confirmation
Disallow: /browser/error
Disallow: /switch-to-ecosia
Crawl-delay: 10

User-agent: ia_archiver
Disallow: /

User-agent: Twitterbot
Allow: /search?*&cpr=*
Allow: /search?cpr=*

sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
TLS Certificate Expiry & Recommendations
59 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.ecosia.org

https://www.ecosia.org

164 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.ecosia.org200164 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3105::ac40:9647, 2a06:98c1:310d::6812:25b9
Got: 2 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3105::ac40:9647, 2a06:98c1:310d::6812:25b9 Connection Reachable (2 ms)
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ecosia.org/
301https://ecosia.org/

Preferred variant: www

HTTP → HTTPS

301http://www.ecosia.org/ https://www.ecosia.org/

Consistent

A+
Domain Intelligence
ecosia.org — via Amazon Registrar, Inc., 16 years, 8 months old
PASS
ecosia.org — via Amazon Registrar, Inc., 16 years, 8 months old
Info::
Domain registered until Oct 4, 2026 (6 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: Amazon Registrar, Inc.
Domain expiry

84 days

October 4, 2026

SSL certificate

59 days

Issued by Google Trust Services

Domain age

16 years, 8 months

Registered October 4, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a14:71c0::2

Registrar

Amazon Registrar, Inc.

Lock status unknown 4 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
Registrar Amazon Registrar, Inc.
Created October 4, 2009 (16 years, 8 months ago)
Expires October 4, 2026 (6 months)
Last Updated September 4, 2025
Name Servers ns-1130.awsdns-13.org, ns-1717.awsdns-22.co.uk, ns-327.awsdns-40.com, ns-815.awsdns-37.net
DNSSEC Not enabled
Hosting
IP Address 2a14:71c0::2
Data source: rdap (0.4s)

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

A+
HTTP Probe Timing
Total 115 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
43 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.
115 ms
Total Time Total request time from DNS lookup through full response.
116 ms

Connection waterfall

DNS Lookup 43 ms TCP Connect 2 ms TLS Handshake 6 ms Server Processing 64 ms Content Transfer 1 ms
A
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9e7252e9e8180d00-EWR
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: 9e7252e9e8180d00-EWR
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback