Skip to content
https://habitat.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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 301-redirects to HTTPS

www / non-www

200https://www.habitat.org/
200https://habitat.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • 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
2 A records, 166 ms lookup
PASS
2 A records, 166 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 3.92.148.23, 54.156.215.232
Info::
No IPv6 (AAAA) records
Info::
8 nameserver(s) configured
Got: dns3.easydns.ca, dns2.easydns.net, ns0.dnsmadeeasy.com, ns2.dnsmadeeasy.com, dns1.easydns.com, ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com
Info::
1 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: 166 ms
Got: 166 ms
A3.92.148.23, 54.156.215.232
AAAA
CNAME
NSdns3.easydns.ca, dns2.easydns.net, ns0.dnsmadeeasy.com, ns2.dnsmadeeasy.com, dns1.easydns.com, ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com
MX
0 habitat-org.mail.protection.outlook.com
TXT
docusign=20df783a-b7fe-483a-9aed-d34cdaa90f6d
google-site-verification=TgVQmgjkMbtRJlLIf0wqSvOa4uv2YLvgWA8hJlbk5JQ
K13vYAJ6TN5gpdPSB7GUd2CwTsEGaMm2dCBQS8eXDO2Fx8IQqaI5XM6HHoIrqI1wPvD/QvcO3cj9UWhy...
zoho-verification=zb16446596.zmverify.zoho.com
5t67rd5ks28dx955sxrkpvn7c9v9ft0l
MS=ms45708025
d0bb8af25b0b4c6f920f252efce6f651
00DU800000C2Ok5=1TBU80000000DoT
CBV9zFbYTT7Jb5h5BMtEgmUXu3oCYDbWQrDNv+83GJm+WZxG/sVp1xlpnTxdq2SW+CgiDkjHZE6xdeFP...
nintex.5f638a924dc53a00721b45b5
apple-domain-verification=KXumtuiSfafUEAY4_2Kyw9QfDKHF-oI9BRNQm-DLezA
smartsheet-site-validation=4jhb4ifuWehi7wAT9kzY1umrzAXlzHhi
MS=ms35767615
atlassian-domain-verification=Lv4CpyoFK/ckEPvMBRqAOxH9hwo4wW3lfxGrP2ra/3pY2TaUFR...
google-site-verification=qDX_A-fS1cAA6YAruBWM4wahTKQJnlb9J7OnhmYOyGQ
SPF v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:sp...
CAALookup not available with standard resolver
Resolved in 166 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
Redirect Chain
1 redirect(s), 825 ms total
PASS
1 redirect(s), 825 ms total
Info::
Single redirect
Got: https://habitat.org → https://www.habitat.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 825 ms total
Got: 825 ms

https://habitat.org

310 ms · HTTP/1.1

301

https://www.habitat.org/

516 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://habitat.org301310 msHTTP/1.1nginx
2https://www.habitat.org/200516 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 2053 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 2053 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed

# Donation paths
Disallow: /donate/review.aspx

A+
Domain Intelligence
habitat.org — via Network Solutions, LLC, 32 years, 7 months old, hosted on AWS
PASS
habitat.org — via Network Solutions, LLC, 32 years, 7 months old, hosted on AWS
Info::
Domain registered until Feb 19, 2030 (3 years, 10 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: Network Solutions, LLC
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: AWS
Got: AS14618
Domain expiry

1344 days

February 19, 2030

SSL certificate

137 days

Issued by Entrust Limited

Domain age

32 years, 7 months

Registered February 18, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

3.92.148.23

Registrar

Network Solutions, LLC

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 Network Solutions, LLC
Created February 18, 1994 (32 years, 7 months ago)
Expires February 19, 2030 (3 years, 10 months)
Last Updated December 26, 2024
Name Servers dns1.easydns.com, dns2.easydns.net, dns3.easydns.ca, ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 3.92.148.23
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

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

Connection waterfall

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

Send Feedback