Skip to content
https://eatright.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.eatright.org/
200https://eatright.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 24 ms lookup
PASS
2 A records, 24 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 20.114.183.63, 20.110.197.31
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns61.domaincontrol.com, ns62.domaincontrol.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: 24 ms
Got: 24 ms
A20.114.183.63, 20.110.197.31
AAAA
CNAME
NSns61.domaincontrol.com, ns62.domaincontrol.com
MX
0 eatright-org.mail.protection.outlook.com
TXT
docusign=7c3496b3-453b-44b7-94e7-66c6c38b0805
jbd50233toft91qlg50241ehdj
hqasoq1hmu503ohrq8ph3v4con
SPF v=spf1 include:_u.eatright.org._spf.dmarcla.com ~all
8vf5406bhao7i3rqp9vsf3i102
apple-domain-verification=5XLWXNqAopHbYsHO
google-site-verification=XT9gwkh5MXCjEvJqEedE61kwEcPWwEE8whCnjtYfRYY
facebook-domain-verification=czh678pfzzupd02e37pedxbnokvt2n
google-site-verification=cd4sdwBUvImcvwtzuyK2hBebXnutS4oYfn9x7Wr-Akk
v9nnduqs0evmm813v3bdheib61
sophos-domain-verification=dca01926d270f703a9f175d4ffa1200899ec9634897199e905d11...
qhh8cgo4fh9qouvpvv4cql5kg3
cisco-ci-domain-verification=5d9888e659ff88c63366db82ff9000535352658395abfb19089...
aos0jt0l5ajb6ihivbc5dj2pmp
o2phaqmo6i170ij5ch76ui3rv7
pinterest-site-verification=8e344098c0c6d2f4288e51cb170de84b
logmein-verification-code=b3538b55-f839-4577-a754-c8041e45f7dc
CAALookup not available with standard resolver
Resolved in 24 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), 834 ms total
PASS
1 redirect(s), 834 ms total
Info::
Single redirect
Got: https://eatright.org → https://www.eatright.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 834 ms total
Got: 834 ms

https://eatright.org

317 ms · HTTP/1.1

301

https://www.eatright.org/

517 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://eatright.org301317 msHTTP/1.1Microsoft-IIS/10.0
2https://www.eatright.org/200517 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 966 URLs
PASS
robots.txt present, sitemap with 966 URLs
Info::
robots.txt is present
Got: 315 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 966 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 315 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /sitecore

Disallow: /sitecore/

Allow: /

Disallow: /app_config/

Disallow: /app_data/

Disallow: /bin/

Disallow: /scripts/

Disallow: /sitecore modules/

Disallow: /search-results?keyword=*

Disallow: /account/login?*

Disallow: /login?*


Sitemap: http://www.eatright.org/sitemap.xml


A+
Domain Intelligence
eatright.org — via GoDaddy.com, LLC, 31 years, 1 months old, hosted on Microsoft Azure
PASS
eatright.org — via GoDaddy.com, LLC, 31 years, 1 months old, hosted on Microsoft Azure
Info::
Domain registered until Aug 21, 2028 (2 years, 4 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: GoDaddy.com, 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: Microsoft Azure
Got: AS8075
Domain expiry

799 days

August 21, 2028

SSL certificate

174 days

Issued by GoDaddy.com, Inc.

Domain age

31 years, 1 months

Registered August 22, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.110.197.31

Registrar

GoDaddy.com, LLC

Unlocked 2 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 GoDaddy.com, LLC
Created August 22, 1995 (31 years, 1 months ago)
Expires August 21, 2028 (2 years, 4 months)
Last Updated June 18, 2024
Name Servers ns61.domaincontrol.com, ns62.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 20.110.197.31
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
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 294 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
67 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
137 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
294 ms
Total Time Total request time from DNS lookup through full response.
295 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 67 ms TLS Handshake 137 ms Server Processing 68 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