Skip to content
https://usgbc.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
C
Crawlability
Action
robots.txt present, sitemap with 164 URLs
REVIEW
robots.txt present, sitemap with 164 URLs
Info::
robots.txt is present
Got: 2357 bytes
Critical::
robots.txt blocks all crawlers
Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 164 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Disallow: / for all user-agents prevents search engines from indexing any page. This will remove the site from search results.

Why this matters

Disallow: / in robots.txt blocks every search crawler — the site becomes invisible in organic search.

Learn more

Common deployment mistake: a staging robots.txt with `User-agent: * / Disallow: /` ships to prod. The site falls out of search results within days. Verify your robots.txt is the production-intended version. If this is intentional (private site), no action needed.

Source: Google Search Central

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 2357 B Sitemaps referenced 0 User-agents Bingbot, Twitterbot, bedrockbot, *, Googlebot Blocking Yes — all crawlers blocked
#
# 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: Googlebot
User-agent: Bingbot
User-agent: Twitterbot
Crawl-delay: 5

# 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

#Ui Pages
Allow: /people/*
Allow: /education/*
Allow: /articles/*
Allow: /credits/*
Allow: /projects/*
Allow: /chapters/*
Allow: /organization/*
Allow: /community/*
Allow: /resources/*
Allow: /store/*
Allow: /merchandise/*
Allow: /help/*
Allow: /contactus
Allow: /leedaddenda/*

User-agent: bedrockbot
Allow: /perform/*
Allow: /articles/*
Allow: /education/*
Allow: /credits/*
Allow: /education-listing/*

# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /sites/default/files/*.pdf
Disallow: /sites/default/files/*.doc
Disallow: /sites/default/files/*.docx
Disallow: /sites/default/files/*.xls
Disallow: /sites/default/files/*.xlsx
Disallow: /sites/default/files/*.ppt
Disallow: /sites/default/files/*.pptx
Disallow: /README.txt
Disallow: /web.config
# 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/
# 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/

User-agent: *
Disallow: /

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.usgbc.org/
200https://usgbc.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://usgbc.org/ https://usgbc.org

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0024af19ea5455-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f0024af19ea5455-CDG
A+
DNS Records
2 A records, 99 ms lookup
PASS
2 A records, 99 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.140.116, 172.66.134.150
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::ac42:8c74, 2606:4700:10::ac42:8696
Info::
2 nameserver(s) configured
Got: nina.ns.cloudflare.com, art.ns.cloudflare.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: 99 ms
Got: 99 ms
A172.66.140.116, 172.66.134.150
AAAA2606:4700:10::ac42:8c74, 2606:4700:10::ac42:8696
CNAME
NSnina.ns.cloudflare.com, art.ns.cloudflare.com
MX
0 usgbc-org.mail.protection.outlook.com
TXT
atlassian-domain-verification=wIX9Gbo0fgTYgFcEEjMWKgdWaj6C79AhoTJwuwI6LxdmW0r6Ph...
SPF v=spf1 ip4:66.150.113.91/32 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243....
smartsheet-site-validation=j3b6yGdRPH6BxLgNVcRDh5-vR1ZM3HDm
7116e21ec95141e39a59775f806806ea
google-site-verification=HzApLQOl-d4MlUIFd0mRuYNazmSkRasVekRVuY0uYRI
google-site-verification=_7X8df_j_-cvvSNq8c7L6z8oRAlQqos8R-iSQyl1E0Y
google-site-verification=rftUr-nz71pFfL2BeXYb4v7drtHudo9c3UnZdIAWD1w
blitz=mu-d6a2e3e2-f4c0e8a1-59115055-321b6c2f
ufTTHKbjEAwsJuNCvvsUBrS0h+HPlhUiMOuAkxI6juBoCExL5eejSSyNqJXeyMVqNRJ7IdB/yPMepgVw...
v=DKIM1;t=s;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCn798hW2rMZm+iW7EEsbQsjR7t57...
pardot413862=2dc49ff8d20c5c54d0aad6674f401b58ce2e7f5c93ac4161ae8002a296e64dd3
notion-domain-verification=gUQ4adR8LUaHLVKlIY6dpfzqRR6D65TmWP8ie7Hgydh
smartsheet-site-validation=xIoKZ_leTYDB8y7fIltH6itfsE5Icd8l
v=verifydomain MS=ms41471662
atlassian-domain-verification=GVLfB3Ld6wcglQaObTuNIiK5eIw2aXP7keKvRyRE5ZmXP6OKdX...
figma-domain-verification=004a2a95ce6cff6448a3495dc96389bfc437b235e3ac0ba962447a...
dropbox-domain-verification=kewrkh6e1rpa
miro-verification=84bc4563ae07463018d23c0509b9cdd47a1d0de2
anthropic-domain-verification-6e0aj4=KlQL33en8pr1Ee83UUt8iQbsI
133c4af53f09da02aa4f4af0d400bddd8234aec03c4982a7e2f265103d9c7fcc
00d400000009uedeau
blitz=mu-82bbced8-545e6867-9f252e8d-9d534997
sophos-domain-verification=ca7be9b5058c2ba7ea511d8dfee0199c3ceb3e5abf969f674d947...
IepxpxUACWbaekmBNvlGHQXmXpFGV8Rz72pk+VmKiY7reCIcthTDjy43C3qJJ2mnXGO0Zw0nKzVGGYTi...
google-site-verification=aZwjgbxwI66QRPXZLYsIGq9V7mdcNQnwhIJej_fNjOY
MS=ms99119295
google-site-verification=_5Ff80ZihUQ4Boj_EQPG0a2OdwNZ34XmPTNSUDqzUJU
CAALookup not available with standard resolver
Resolved in 99 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), 168 ms total
PASS
1 redirect(s), 168 ms total
Info::
Single redirect
Got: https://usgbc.org → https://www.usgbc.org/ (301)
Info::
WWW normalization redirect

https://usgbc.org

63 ms · HTTP/1.1

301

https://www.usgbc.org/

105 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://usgbc.org30163 msHTTP/1.1cloudflare
2https://www.usgbc.org/200105 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::ac42:8c74, 2606:4700:10::ac42:8696
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::ac42:8c74, 2606:4700:10::ac42:8696 Connection Reachable (17 ms)
A
Domain Intelligence
usgbc.org — via Tucows Domains Inc., 30 years, 2 months old
PASS
usgbc.org — via Tucows Domains Inc., 30 years, 2 months old
Warning::
Domain expires in 79 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 10, 2026
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: Tucows Domains Inc.
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

24 days

July 10, 2026

SSL certificate

322 days

Issued by Sectigo Limited

Domain age

30 years, 2 months

Registered July 11, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:8c74

Registrar

Tucows Domains Inc.

Unlocked 2 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 Tucows Domains Inc.
Created July 11, 1996 (30 years, 2 months ago)
Expires July 10, 2026 (2 months)
Last Updated July 14, 2025
Name Servers art.ns.cloudflare.com, nina.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::ac42:8c74
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 36 ms TCP Connect 17 ms TLS Handshake 23 ms Server Processing 20 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback