ecosia.org
HTTPS & TLS
100/100A+- HTTPS certificateGoogle Trust Services10/10
HTTPS with a valid certificate from Google Trust Services.
- Certificate expiry454/4
The certificate is valid for another 45 days.
- TLS versionTLS 1.34/4
Negotiates TLS 1.3, the current protocol: faster handshakes, forward secrecy always.
- Old protocols3/3
Refuses the retired TLS 1.0 and 1.1.
- Key strengthECDSA P-2562/2
A strong key: ECDSA P-256.
- HTTP → HTTPS3013/3
http:// redirects straight to https://.
- HSTS1 year4/4
HSTS tells browsers to use HTTPS only, for 1 year.
- HTTP/2 and HTTP/3HTTP/22/2
HTTP/2.
DNS
100/100A+- Name servers44/4
4 name servers for the domain.
- Name servers answer4/45/5
Every name server answers for the domain, with the same version of the zone.
- DNSSECECDSAP256SHA2563/3
Signed with DNSSEC: resolvers can tell forged answers from real ones.
- CAA recordsamazonaws.com, amazontrust.com, awstrust.com, pki.goog, amazon.com2/2
CAA records name the authorities allowed to issue its certificates.
- MTA-STSpolicy_unreachable0/2
MTA-STS is announced, but its policy file cannot be used.
Serve https://mta-sts.ecosia.org/.well-known/mta-sts.txt with a valid certificate.
- SPF~all4/5
SPF lists the servers allowed to send its mail and marks the rest as suspicious (~all).
- DMARCquarantine5/7
DMARC sends mail that fakes the domain to spam (p=quarantine).
- TLS reporting0.5/0.5
TLS reporting: senders report failed encrypted deliveries.
- DKIMgoogle2/2
A DKIM key is published (selector google), so its mail can be signed.
Web & network
97/100A+- Permissions-Policy0/0.5
No Permissions-Policy: embedded content may ask for camera, microphone or location.
- Content Security Policy3/3
A Content Security Policy limits which scripts the pages run.
- X-Content-Type-Options2/2
X-Content-Type-Options: nosniff stops browsers guessing file types.
- Framing2/2
Other sites cannot frame its pages (clickjacking protection).
- Referrer-Policyorigin-when-cross-origin0.5/0.5
Referrer-Policy limits what other sites learn about where visitors came from.
- IPv64/4
www.ecosia.org is reachable over IPv6 as well as IPv4.
- RPKIvalid4/4
The route to the website is RPKI-valid: networks can reject hijacked announcements of it.
Dependencies
80/100B- DNS providersAmazon Route 533/5
All DNS is with one provider (Amazon Route 53): an outage there takes the domain offline, as Dyn's did in 2016.
- One company for everything5/5
The website, DNS and email do not all hang on one company.
Who runs it
- Website
- Cloudflare
- Google Workspace
Routes
- 172.64.150.0/24AS13335RPKI valid
- 2606:4700:4401::/48AS13335RPKI valid
Name servers
- ns-1130.awsdns-13.orgAmazon Route 53AS16509
- ns-1717.awsdns-22.co.ukAmazon Route 53AS16509
- ns-327.awsdns-40.comAmazon Route 53AS16509
- ns-815.awsdns-37.netAmazon Route 53AS16509
README badge
Show the grade in your README or docs; it updates when the domain is graded again.
[](https://skycisa.com/grade/ecosia.org)Compare with…
What is graded
A valid certificate (an invalid one means F), its expiry against its lifetime, TLS 1.3, no TLS 1.0/1.1 (else at most B), http:// sent straight to https://, HSTS, HTTP/2.
At least two name servers that all answer and agree, DNSSEC, CAA records, and a registration that is not about to expire.
SPF, a DMARC policy that rejects forgeries (none means at most B), MTA-STS and TLS reporting for domains that take mail, DKIM at common selectors.
Content Security Policy, nosniff, framing protection, Referrer- and Permissions-Policy, IPv6, and an RPKI-valid route (invalid means at most C).
DNS from more than one provider, and the website, DNS and email not all with one company.
A+ 95–100 · A 85–94 · B 75–84 · C 65–74 · D 50–64 · F below 50