Skip to content
https://shrm.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
4 PASS 4 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.

B
Redirect Chain
1 redirect(s), 1399 ms total
REVIEW
1 redirect(s), 1399 ms total
Info::
Single redirect
Got: https://shrm.org → https://www.shrm.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://shrm.org
Warning::
Redirect overhead: 1399 ms total
Got: 1399 ms

https://shrm.org

568 ms · HTTP/1.0

302

https://www.shrm.org/

831 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://shrm.org302568 msHTTP/1.0BigIP
2https://www.shrm.org/200831 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.shrm.org/
200https://shrm.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://shrm.org/ https://www.shrm.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

177
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, 1681 ms lookup
PASS
2 A records, 1681 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 52.87.68.153, 35.172.207.137
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1127.awsdns-12.org, ns-1938.awsdns-50.co.uk, ns-202.awsdns-25.com, ns-654.awsdns-17.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
Warning::
DNS resolution is slow (1681 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1681 ms
A52.87.68.153, 35.172.207.137
AAAA
CNAME
NSns-1127.awsdns-12.org, ns-1938.awsdns-50.co.uk, ns-202.awsdns-25.com, ns-654.awsdns-17.net
MX
0 shrm-org.mail.protection.outlook.com
TXT
8q5s22e7r1fi1b32b7qc5fvmdb
9u4efcahd13dk8j8f4cme1h5on
MS=ms36614591
QuPmlhDCxqfbWhX3Pfx+zxBE9OHuNkfmneGuJBGcLdSN0jxR3HUAVzR98WrnbvcJGH/VMaxAEVoUUhQj...
_0sjrj5rssijb4el6ivhhg7gyqth33p6
_9ug97rsgg5ymt6my4qxce1mevno4xsh
apple-domain-verification=kAYe4U0BhVn8kVMn
atlassian-domain-verification=/c/uRWisnzEzdSau9/XUVVN59B3Fg5y639nnAe5AjiLMa8aGMe...
atlassian-domain-verification=LtzG/Z/T89QTpWGE9zaDwODciGv029mdIm/bmJJzeBy0B0u9Ht...
bw=XYQ9pnkfQCx0EwQ8vRLctKjTac0dVvi8iRyd5YaiFfyB
cisco-ci-domain-verification=25500dfa8c124f664b20b3306b4b82b645adf21ee8dfe27f0f7...
docusign=405102df-2627-4c3d-b413-e057c29947fb
facebook-domain-verification=4gegmvw3889l51w8nm2krdnjg1qmcg
formstack-domain-verification=3976db858b927f00aec678b510edd358
g8ppjc8cc6raa9q2nq1hhtfv6t
google-site-verification=QPdgZJSToznf6exbsk5E7B1zNocACO7b6M248yvyZ9M
google-site-verification=ZgGxFCmroRG-WM3BNmYu16YJ6P5630VZl_jc4jYVx-4
google-site-verification=qRFtc9U1mVzVdQDBm-f6smssDR7q01-h6uC2gnBHrks
mandrill_verify.yxKFvvHFVISqUWJ8HTinhQ
mandrill_verify.zpXDiApxhLbb0QN4YcqvNw
onetrust-domain-verification=7ea0aae0bd734243a837a4a61d879022
qcfghbmbshnvf9iifg62vcs53l
qn0ubcp0gp4jgpf468f63krhu6
rTE26zjDyKJ+afjUU1KNLgUA9uykOBLlIogtlSfBAKmBhrnXNXFvKfP3sCmEz+wftdPHBuGLUmvdkWTe...
s4ph1glrvcdvki1urm7g2108bo
status-page-domain-verification=h0qpjpdc8dj9
stripe-verification=4d3ff8cc1ef4bcfcec411f4cfd261342404250eccac27390f1fdaf469e14...
SPF v=spf1 include:spf.protection.outlook.com include:1ex2nvenyc.powerspf.com ~all
vqf30q35rfarvci2auf3r69fvt
CAALookup not available with standard resolver
Resolved in 1681 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 938 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 938 B Sitemaps referenced 1 User-agents *, Pingdom.com_bot, Blackbox Exporter Blocking No — crawling allowed
User-agent: *

Disallow: /errors/*
Disallow: /in/errors/*
Disallow: /mena/errors/*
Disallow: /content/shrm/language-masters/*
Disallow: /content/dam/en/shrm/topics-tools/tools/policies/*
Disallow: /content/dam/en/shrm/topics-tools/tools/toolkits/*
Disallow: /content/dam/en/shrm/topics-tools/tools/how-to-guides/*
Disallow: /content/dam/en/shrm/topics-tools/tools/forms/*
Disallow: /content/dam/en/shrm/topics-tools/tools/white-papers/*
Disallow: /content/dam/en/shrm/topics-tools/tools/presentations/*
Disallow: /content/dam/en/shrm/topics-tools/tools/hr-forms/*
Disallow: /content/dam/en/shrm/topics-tools/tools/job-descriptions/*
Disallow: /content/dam/en/shrm/topics-tools/tools/hr-answers/*
Disallow: /content/dam/en/shrm/topics-tools/tools/express-requests/*
Disallow: /content/dam/en/shrm/research/*
User-agent: Pingdom.com_bot
Disallow: /
User-agent: Blackbox Exporter
Disallow: /


SiteMap: https://www.shrm.org/sitemap-index.xml
A+
Domain Intelligence
shrm.org — via eNom, LLC, 31 years, 4 months old, hosted on AWS
PASS
shrm.org — via eNom, LLC, 31 years, 4 months old, hosted on AWS
Info::
Domain registered until May 10, 2035 (9 years, 2 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: eNom, 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

3224 days

May 10, 2035

SSL certificate

177 days

Issued by GoDaddy.com, Inc.

Domain age

31 years, 4 months

Registered May 9, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.87.68.153

Registrar

eNom, 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 eNom, LLC
Created May 9, 1995 (31 years, 4 months ago)
Expires May 10, 2035 (9 years, 2 months)
Last Updated December 1, 2025
Name Servers ns-1127.awsdns-12.org, ns-1938.awsdns-50.co.uk, ns-202.awsdns-25.com, ns-654.awsdns-17.net
DNSSEC Not enabled
Hosting
IP Address 52.87.68.153
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
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
HTTP Probe Timing
Total 571 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
282 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
96 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
98 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
571 ms
Total Time Total request time from DNS lookup through full response.
572 ms

Connection waterfall

DNS Lookup 282 ms TCP Connect 96 ms TLS Handshake 98 ms Server Processing 95 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