Skip to content
https://emerald.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
80 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

80
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9eff6db23bc29e67-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9eff6db23bc29e67-CDG
A+
DNS Records
2 A records, 40 ms lookup
PASS
2 A records, 40 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.20.31.133, 172.66.167.1
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::6814:1f85, 2606:4700:10::ac42:a701
Info::
2 nameserver(s) configured
Got: athena.ns.cloudflare.com, derek.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: 40 ms
Got: 40 ms
A104.20.31.133, 172.66.167.1
AAAA2606:4700:10::6814:1f85, 2606:4700:10::ac42:a701
CNAME
NSathena.ns.cloudflare.com, derek.ns.cloudflare.com
MX
0 emerald-com.mail.protection.outlook.com
TXT
MS=ms64303931
amazonses:9b8LJOXdom5cjAhHii+f8zQiJRcoeQdwOJLd8dHwcfM=
bw=zDK0WVxhoN8SWgSSBl1ruTnzpJaJ2i5cIxDGlH5pLtmm
SPF v=spf1 ip4:203.200.192.105 ip4:107.21.37.86 ip4:203.200.192.109 ip4:134.213.195....
google-site-verification=M4d9bgypRCGN4DusH6fpUChU5qM-Ny24fGSxnodo4uk
google-site-verification=B801E-BzdbgU3YKlifSz5is0NHt5dKgbe2D7cyh77Hg
UK-federation-domain-verification=fb87a4a118cec0e11a2ed9799138f0eb
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDpDCE+FicPuc28f0mppTrjpIHMXo...
k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCnIo1zyP/0vzEGusrGEDK1RI3CXK...
CAALookup not available with standard resolver
Resolved in 40 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://emerald.com → https://www.emerald.com/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://emerald.com

https://emerald.com

59 ms · HTTP/1.1

302

https://www.emerald.com/

109 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://emerald.com30259 msHTTP/1.1cloudflare
2https://www.emerald.com/403109 msHTTP/1.1cloudflare

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

A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::6814:1f85, 2606:4700:10::ac42:a701
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::6814:1f85, 2606:4700:10::ac42:a701 Connection Reachable (17 ms)
A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1194 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references 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

robots.txt 200 OK
Size 1194 B Sitemaps referenced 3 User-agents 008, *, ChatGPT-User, OAI-SearchBot, Perplexity-User, PerplexityBotClaude-SearchBot, Claude-User Blocking No — crawling allowed

User-agent: 008

Disallow: /


User-agent: *

Disallow: /bin/

Disallow: /config/

Disallow: /app_data/

Disallow: /dlls/

Disallow: /App_Themes/

Disallow: /signin.aspx

Disallow: /searchresults.aspx

Disallow: /search-results

Disallow: /advancedsearch.aspx

Disallow: /advanced-search

Disallow: /DownloadFile/

Disallow: /downloadimage.aspx

Disallow: /Citation/Download

Disallow: /Shibboleth.sso/

Disallow: /SignInShibboleth.aspx

Disallow: /lookup/external-ref

Disallow: /user/logout

Disallow: /cgi/pmidlookup

Disallow: /Themes/Client/app/img/favicons/manifest.json

Disallow: /lookup/google-scholar

Disallow: /store/*

Allow: /cassette.axd/stylesheet/

Allow: /cassette.axd/script/

Allow: /cassette.axd/manifest.xml

Disallow: /*.axd

Disallow: /specificToClient1/


User-agent: ChatGPT-User

Allow: /

User-agent: OAI-SearchBot

Allow: /

User-agent: Perplexity-User

Allow: /

User-agent: PerplexityBotClaude-SearchBot

Allow: /

User-agent: Claude-User

Allow: /


Sitemap:https://www.emerald.com/data/sitemap/sitemap_Collections.xml

Sitemap: https://www.emerald.com/data/sitemap/Site_1/sitemap_books_site1.xml

Sitemap: https://www.emerald.com/data/sitemap/sitemap.xml


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.emerald.com/
200https://emerald.com/

HTTP → HTTPS

301http://emerald.com/ https://emerald.com/

Consistent

A+
Domain Intelligence
emerald.com — via GoDaddy.com, LLC, 29 years, 3 months old
PASS
emerald.com — via GoDaddy.com, LLC, 29 years, 3 months old
Info::
Domain registered until Jun 19, 2027 (1 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: 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.
Domain expiry

337 days

June 19, 2027

SSL certificate

80 days

Issued by Google Trust Services

Domain age

29 years, 3 months

Registered June 20, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::6814:1f85

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 June 20, 1997 (29 years, 3 months ago)
Expires June 19, 2027 (1 years, 2 months)
Last Updated February 12, 2026
Name Servers athena.ns.cloudflare.com, derek.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::6814:1f85
Data source: rdap (0.1s)

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 98 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
40 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.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
99 ms
Total Time Total request time from DNS lookup through full response.
99 ms

Connection waterfall

DNS Lookup 40 ms TCP Connect 16 ms TLS Handshake 22 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