Skip to content
https://hrc.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://hrc.org/ https://hrc.org:443/

Consistent

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

Certificate validity

185
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
3 A records, 25 ms lookup
PASS
3 A records, 25 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 44.224.169.121, 54.200.139.59, 35.82.156.214
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1411.awsdns-48.org, ns-1711.awsdns-21.co.uk, ns-2.awsdns-00.com, ns-816.awsdns-38.net
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: 25 ms
Got: 25 ms
A44.224.169.121, 54.200.139.59, 35.82.156.214
AAAA
CNAME
NSns-1411.awsdns-48.org, ns-1711.awsdns-21.co.uk, ns-2.awsdns-00.com, ns-816.awsdns-38.net
MX
0 hrc-org.mail.protection.outlook.com
TXT
canva-site-verification=BU27z66eZ1H3uSRJoHTE4w
google-site-verification=ZdTfSUGbYtx25b0fbZvTSOPE-7hwRtd8hfwQIrxngjg
mentimeter-5be229f2-30ba-466d-ae47-f7b708e4045b
u/1JjvUHe7qT1wXfawRv9WVHi8eTHO/vMvbq7YWZ9Ok=.
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:spf.protection.o...
validity-domain-monitoring=8GySauzDP4E6yVmUnJCODVPzZ
CAALookup not available with standard resolver
Resolved in 25 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), 816 ms total
PASS
1 redirect(s), 816 ms total
Info::
Single redirect
Got: https://hrc.org → https://www.hrc.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 816 ms total
Got: 816 ms

https://hrc.org

94 ms · HTTP/1.1

301

https://www.hrc.org/

722 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hrc.org30194 msHTTP/1.1nginx
2https://www.hrc.org/200722 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 52 URLs
PASS
robots.txt present, sitemap with 52 URLs
Info::
robots.txt is present
Got: 705 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 52 entries
Info::
Sitemap index with 52 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 705 B Sitemaps referenced 2 User-agents *, GPTBot, Google-Extended, PerplexityBot Blocking No — crawling allowed
# robots.txt for https://www.hrc.org/

sitemap: https://www.hrc.org/sitemaps-2-sitemap.xml
sitemap: https://www.hrc.org/es/sitemaps-2-sitemap.xml

    # live - don't allow web crawlers to index cpresources/ or vendor/

    User-agent: *
    Disallow: /cpresources/
    Disallow: /vendor/
    Disallow: /.env
    Disallow: /cache/


# Disallow ChatGPT bot, as there's no benefit to allowing it to index your site
User-agent: GPTBot
Disallow: /

# Disallow Google Bard and Vertex AI bots, as there's no benefit to allowing it to index your site
User-agent: Google-Extended
Disallow: /

# Disallow Perplexity bot, as there's no benefit to allowing it to index your site
User-agent: PerplexityBot
Disallow: /

sitemap.xml 200 OK
Type Sitemap Index URLs 52 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
hrc.org — via Network Solutions, LLC, 29 years, 7 months old, hosted on AWS
PASS
hrc.org — via Network Solutions, LLC, 29 years, 7 months old, hosted on AWS
Info::
Domain registered until Feb 20, 2033 (6 years, 11 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: AS16509
Domain expiry

2443 days

February 20, 2033

SSL certificate

185 days

Issued by Amazon

Domain age

29 years, 7 months

Registered February 19, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

35.82.156.214

Registrar

Network Solutions, LLC

Unlocked 4 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 19, 1997 (29 years, 7 months ago)
Expires February 20, 2033 (6 years, 11 months)
Last Updated February 25, 2023
Name Servers ns-1411.awsdns-48.org, ns-1711.awsdns-21.co.uk, ns-2.awsdns-00.com, ns-816.awsdns-38.net
DNSSEC Not enabled
Hosting
IP Address 35.82.156.214
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.2s)

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 75 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
6 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
22 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.
75 ms
Total Time Total request time from DNS lookup through full response.
75 ms

Connection waterfall

DNS Lookup 6 ms TCP Connect 22 ms TLS Handshake 23 ms Server Processing 25 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