Skip to content
https://hbr.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
D
TLS Certificate Expiry & Recommendations
Action
8 days until leaf cert expires — 6 issues to address
FIX

Certificate validity

8
days left
0d 30d 60d 90d+
Renew urgently — under 14 days remaining

Recommended actions

  • Renew certificate — 8 days remaining
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1053 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / 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 1053 B Sitemaps referenced 0 User-agents ChatGPT-User, Google-Extended, *, 008, FeedBurner/1.0, GPTBot, CCBot Blocking No — crawling allowed
User-Agent: *
Disallow: /resources/
Allow: /resources/js
Allow: /resources/css
Allow: /resources/images/
Allow: /resources/xml/sitemaps/
Disallow: /fastanswers
Disallow: /my-library*
Disallow: /email-colleague/
Disallow: /add-to-cart/
Disallow: /login*
Disallow: /shopping-cart/
Disallow: /shipping-payment
Disallow: /review-order
Disallow: /order/thank-you/
Disallow: /content/ipad/
Disallow: /newsletters*
Disallow: /product/recommended*
Disallow: /webinar-assessment
Disallow: /search*
Disallow: /academic-subscriptions
Disallow: /alumni-subscriptions
Allow: /resources/html/infographics/2018/ceo-activism-desktop/index.html
Disallow: /resources/html/error/404.html
Disallow: /sponsored/2022/10/disruptors-who-are-changing-their-industries
Disallow: /api/recaptcha/enabled
Disallow: /register?*
Disallow: /resources/css/webscripts.css
User-Agent: 008
Disallow: /
User-Agent: FeedBurner/1.0
Allow: /resources/xml/
User-agent: GPTBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: ChatGPT-User
Disallow: /
User-agent: Google-Extended
Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
DNS Records
4 A records, 133 ms lookup
PASS
4 A records, 133 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 52.84.174.73, 52.84.174.128, 52.84.174.127, 52.84.174.105
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-469.awsdns-58.com, ns-1877.awsdns-42.co.uk, ns-604.awsdns-11.net, ns-1175.awsdns-18.org
Info::
2 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: 133 ms
Got: 133 ms
A52.84.174.73, 52.84.174.128, 52.84.174.127, 52.84.174.105
AAAA
CNAME
NSns-469.awsdns-58.com, ns-1877.awsdns-42.co.uk, ns-604.awsdns-11.net, ns-1175.awsdns-18.org
MX
10 mxb-00044a01.gslb.pphosted.com
10 mxa-00044a01.gslb.pphosted.com
TXT
atlassian-domain-verification=5VnB9cXf8cZ+rqMksjlq1KyEzUSjGsBJ5irmtvOZtpwtq6AsKS...
docusign=59df337d-04fe-422f-bd8e-438fc3e80d21
webexdomainverification.4C675B8B1892B136E053AB06FC0A3F65=7b2ac320-8920-4cf1-826d...
ciscocidomainverification=3a5e2e428cc891b6aef0b7598537338dd5c2bf8fe96326d58d87f6...
extensis-domain-verification=3decd987-0352-469b-8111-a273b429588a
google-site-verification=0fyEgLpijqbt_OMG0ncBIK4G153eKqHF7UeGfTZgZk0
MS=ms51679339
sip=m699vbpan7kdoitobogsq38e1k
smartsheet-site-validation=76f6Fdn8EnnOgbwX-KcCnJ5Nj66wRUeo
facebook-domain-verification=hvrm85rd5hvr18o50vzpd1lprkjg76
_1nl5kysnqxswpmo75e1u1fdcbs0fptr
knowbe4-site-verification=f00a4d6e618b4a00b6f39e0b4c9e093f
google-site-verification=ikLo_eYH7jY56yB4qtVoDTxY9WUWl7NkUEsM-UB6DT0
openai-domain-verification=dv-yzIW4FvevpXrgKYrQ9Ndlm4V
lyncdiscover = seh3q1rpvadu98fpk213q7htq2
google-site-verification=P1JGD_hnkAqlxSPmsFW_M2nifpmJC2iBjnfmKi1uJCc
SPF v=spf1 ip4:167.89.5.215 include:hbsp.harvard.edu include:amazonses.com include:u...
google-site-verification=o-E502ZnlfSSAM2JRb0RUfIxROmYDcYVOZnzlVRknS0
Wo71J1PNbWKkAikjb4WeqxCjBcNQwf6hcll0LJM6s9peRMF1ImcaCENQfddffLROaJY6wZHW2jrUsDNX...
onetrust-domain-verification=0df7d79642a64b338bb91818045b158d
CAALookup not available with standard resolver
Resolved in 133 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://hbr.org

https://hbr.org

489 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hbr.org200489 msHTTP/1.1
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.hbr.org/
200https://hbr.org/

Preferred variant: non-www

HTTP → HTTPS

301http://hbr.org/ https://hbr.org/

Consistent

A+
Domain Intelligence
hbr.org — via MarkMonitor Inc., 29 years, 9 months old, hosted on AWS
PASS
hbr.org — via MarkMonitor Inc., 29 years, 9 months old, hosted on AWS
Info::
Domain registered until Dec 4, 2027 (1 years, 7 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: MarkMonitor 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.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

508 days

December 4, 2027

SSL certificate

8 days

Issued by DigiCert Inc

Domain age

29 years, 9 months

Registered December 5, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

52.84.174.105

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created December 5, 1996 (29 years, 9 months ago)
Expires December 4, 2027 (1 years, 7 months)
Last Updated November 7, 2025
Name Servers ns-1175.awsdns-18.org, ns-1877.awsdns-42.co.uk, ns-469.awsdns-58.com, ns-604.awsdns-11.net
DNSSEC Not enabled
Hosting
IP Address 52.84.174.105
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.8s)

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

Connection waterfall

DNS Lookup 39 ms TCP Connect 16 ms TLS Handshake 19 ms Server Processing 211 ms Content Transfer 18 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: CDG50-P1)
Got: x-amz-cf-id: krScNtpTxePriffoMt_zgzpyXzmJ51ARcvdEc-OQo80VVSrFaF291Q==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: krScNtpTxePriffoMt_zgzpyXzmJ51ARcvdEc-OQo80VVSrFaF291Q==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback