Skip to content
https://greenly.earth

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
17
10 PASS 7 REVIEW
C
DNSSEC
Action
Zone signed but parent has no DS record
REVIEW
Zone signed but parent has no DS record
Warning::
DNSSEC keys published but parent zone has no DS record
The zone publishes DNSKEY records but the registry has not been updated with the corresponding DS record. From a validating resolver's perspective the domain is unsigned. Submit the DS record to your registrar to complete the delegation.
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 104.20.22.14: lookup 104.20.22.14: 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 172.66.165.10: lookup 172.66.165.10: 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 2606:4700:10::6814:160e: lookup 2606:4700:10::6814:160e: 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 2606:4700:10::ac42:a50a: lookup 2606:4700:10::ac42:a50a: 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.
B
HTTP Probe Timing
Total 1050 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
16 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
897 ms
Total Time Total request time from DNS lookup through full response.
1.05 s

Connection waterfall

DNS Lookup 16 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 871 ms Content Transfer 153 ms
B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
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.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 25 ms lookup
PASS
2 A records, 25 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.22.14, 172.66.165.10
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:160e, 2606:4700:10::ac42:a50a
Info::
2 nameserver(s) configured
Got: carl.ns.cloudflare.com, hadlee.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 25 ms
Got: 25 ms
A104.20.22.14, 172.66.165.10
AAAA2606:4700:10::6814:160e, 2606:4700:10::ac42:a50a
CNAME
NScarl.ns.cloudflare.com, hadlee.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
1password-site-verification=IBRPPHVW6JGATM36AC3P7562WI
6d7bae5ae08c71e579ef7f3955510b1f
MS=A6C811CBEF1D1F180BC7FB4A6297CCC681B2DFB1
MS=FC29FA6BABAFF85BD0E47E35AF2B2735ADFBA145
anthropic-domain-verification-v98d29=8f6G7YhD9oyo0ER9dlGIEjOS4
brevo-code:ddffbbce680da454c308588f579f13f4
cloudflare_dashboard_sso=953248c8e2ff28d13d801710c5d99cb1
cursor-domain-verification-1bnvk8=y47HLRgUxScIGMPgZLRaTFmee
google-site-verification=JahnncPu3j4vP6aMSABWxEpoJ6Uhl9nqsiavK6FxrGc
google-site-verification=Q464QVvgWjpIf7F8pM6t4eQALKT1oZr-SkT_OPRMooQ
google-site-verification=eFXoFvoRiYDvwugzb0iqy6hgfHeODW0vc8AYi865RjE
hubspot-domain-verification=ZmRhODUyYmYtZWU3ZS00NTA0LThlNzgtYzBmODg3MGI1NTJm
mongodb-site-verification=igzryDgo8HlaIkN1l3kyLSAK6Z8bHG40
notion-domain-verification=DRTaIydmznmoAak81qDxRR7m1o0qy9Ar7V40hgHLaGi
pandadoc-domain-verification=YeAAqZxLYkTCY7frePXoVG
proxy-ssl.webflow.com
stripe-verification=c528b6bbdf569358a4147c98c7919a827ce22bb06d7d57867ceb2d9a0ecc...
SPF v=spf1 include:_spf.google.com include:amazonses.com include:spf.sendinblue.com ...
yandex-verification: 4fd08135fc0c2d4a
CAALookup not available with standard resolver
Resolved in 25 ms
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 9ms across 3 resolvers (spread 11ms)
PASS
Mean 9ms across 3 resolvers (spread 11ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 10ms
Got: 10ms via 9.9.9.9:53
Info::
Google: 15ms
Got: 15ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://greenly.earth

https://greenly.earth

932 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://greenly.earth200932 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::6814:160e, 2606:4700:10::ac42:a50a
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:160e, 2606:4700:10::ac42:a50a Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 842 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 842 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# *
User-agent: *
Allow: /

# Block all crawlers for /climate-journey
User-agent: *
Disallow: /climate-journey/

# Block all crawlers for /climate-journey
User-agent: *
Disallow: /engagement-climatique/

# Block all crawlers for /leaf-media?s=
User-agent: *
Disallow: /leaf-media?s=*$

# Host
Host: https://greenly.earth

# Sitemaps
Sitemap: https://greenly.earth/sitemap.xml

# Next.JS Crawl Budget Performance Updates
# Block files ending in .json, _buildManifest.js, _middlewareManifest.js, _ssgManifest.js, and any other JS files
# The asterisks allows any file name
# The dollar sign ensures it only matches the end of an URL and not a oddly formatted url (e.g. /locations.json.html) 
Disallow: /*.json$
Disallow: /*_buildManifest.js$
Disallow: /*_middlewareManifest.js$
Disallow: /*_ssgManifest.js$
Disallow: /*.js$
Disallow: /*.woff2$

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

301https://www.greenly.earth/
200https://greenly.earth/

Preferred variant: non-www

HTTP → HTTPS

301http://greenly.earth/ https://greenly.earth/

Consistent

A+
Domain Intelligence
greenly.earth — via OVH sas, 6 years, 7 months old
PASS
greenly.earth — via OVH sas, 6 years, 7 months old
Info::
Domain registered until Jan 1, 2028 (1 years, 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: OVH 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.
Domain expiry

538 days

January 1, 2028

SSL certificate

82 days

Issued by Google Trust Services

Domain age

6 years, 7 months

Registered January 1, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:a50a

Registrar

OVH sas

Unlocked 2 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 OVH sas
Created January 1, 2020 (6 years, 7 months ago)
Expires January 1, 2028 (1 years, 6 months)
Last Updated October 14, 2025
Name Servers carl.ns.cloudflare.com, hadlee.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::ac42:a50a
Data source: rdap (1.0s)

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
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: a1436f187af8a24f-SIN
Info::
CDN cache status: DYNAMIC
CDN Detected: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a1436f187af8a24f-SIN
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback