Skip to content
https://www.elastic.co

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
5 PASS 4 REVIEW
C
DNS Records
Action
1 A records, 338 ms lookup
REVIEW
1 A records, 338 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 151.101.78.217
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a04:4e42:12::729
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: dualstack.r2.shared.global.fastly.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Warning::
DNS resolution is slow (338 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 338 ms
A151.101.78.217
AAAA2a04:4e42:12::729
CNAMEdualstack.r2.shared.global.fastly.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 338 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 10240 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 10240 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /guide/en/*/current*
Allow: /guide/en/*/master*
Allow: /guide/$
Allow: /guide$
Allow: /guide/?*
Allow: /guide/cn/elasticsearch$
Allow: /guide/cn/elasticsearch/$
Allow: /guide/cn/elasticsearch/php/$
Allow: /guide/cn/elasticsearch/php$
Allow: /guide/cn/kibana$
Allow: /guide/en/apm$
Allow: /guide/en/apm/$
Allow: /guide/en/apm/agent$
Allow: /guide/en/apm/agent/dotnet$
Allow: /guide/en/apm/agent/dotnet/$
Allow: /guide/en/apm/agent/go$
Allow: /guide/en/apm/agent/go/$
Allow: /guide/en/apm/agent/java$
Allow: /guide/en/apm/agent/java/$
Allow: /guide/en/apm/agent/js-base/1.x/api.html$
Allow: /guide/en/apm/agent/js-base/4.x/configuration.html$
Allow: /guide/en/apm/agent/js-base/4.x/distributed-tracing-guide.html$
Allow: /guide/en/apm/agent/js-base/4.x/intro.html$
Allow: /guide/en/apm/agent/nodejs$
Allow: /guide/en/apm/agent/php$
Allow: /guide/en/apm/agent/python/$
Allow: /guide/en/apm/agent/python/index.html$
Allow: /guide/en/apm/agent/rum-js$
Allow: /guide/en/apm/agent/rum-js/$
Allow: /guide/en/apm/agent/rum-js/2.x$
Allow: /guide/en/apm/agent/swift/$
Allow: /guide/en/apm/get-started$
Allow: /guide/en/apm/get-started/$
Allow: /guide/en/apm/get-started/6.0/install-and-run.html$
Allow: /guide/en/apm/get-started/index.html$
Allow: /guide/en/apm/guide/$
Allow: /guide/en/apm/guide/8.10$
Allow: /guide/en/apm/server$
Allow: /guide/en/apm/server/$
Allow: /guide/en/app-search$
Allow: /guide/en/app-search/$
Allow: /guide/en/app-search/7.17/index.html*
Allow: /guide/en/app-search/8.1/$
Allow: /guide/en/app-search/8.15/$
Allow: /guide/en/app-search/8.18$
Allow: /guide/en/app-search/8.18/index.html*
Allow: /guide/en/cloud-enterprise/$
Allow: /guide/en/cloud-on-k8s$
Allow: /guide/en/cloud-on-k8s/$
Allow: /guide/en/cloud/saas-release-heroku/custom-repository.html*
Allow: /guide/en/cloud/saas-release-heroku/ec-faq.html*
Allow: /guide/en/cloud/saas-release/ec-api-console.html*
Allow: /guide/en/cloud/saas-release/ec-aws-custom-repository.html*
Allow: /guide/en/cloud/saas-release/ec-billing-aws.html*
Allow: /guide/en/cloud/saas-release/ec-billing.html*
Allow: /guide/en/cloud/saas-release/ec-create-deployment.html*
Allow: /guide/en/cloud/saas-release/ec-custom-repository.html*
Allow: /guide/en/cloud/saas-release/ec-getting-started-templates-hot-warm.html*
Allow: /guide/en/cloud/saas-release/ec-getting-started-templates.html*
Allow: /guide/en/cloud/saas-release/ec-reference-hardware.html*
Allow: /guide/en/cloud/saas-release/ec-reference-regions.html*
Allow: /guide/en/cloud/saas-release/ec-release-notes.html*
Allow: /guide/en/cloud/saas-release/ec-restrictions.html*
Allow: /guide/en/cloud/saas-release/ec-scenario_why_are_my_cluster_response_times_suddenly_so_much_worse.html$
Allow: /guide/en/cloud/saas-release/ec-scenario_why_is_performance_degrading_over_time.html*
Allow: /guide/en/cloud/saas-release/ec-security-transport.html*
Allow: /guide/en/cloud/saas-release/ec-version-policy.html*
Allow: /guide/en/cloud/saas-release/security.html*
Allow: /guide/en/ecs$
Allow: /guide/en/ecs-logging/$
Allow: /guide/en/ecs-logging/dotnet/$
Allow: /guide/en/ecs-logging/go-logrus/$
Allow: /guide/en/ecs-logging/go-zap/$
Allow: /guide/en/ecs-logging/java/$
Allow: /guide/en/ecs-logging/nodejs/$
Allow: /guide/en/ecs-logging/overview/$
Allow: /guide/en/ecs-logging/php/$
Allow: /guide/en/ecs-logging/ruby/$
Allow: /guide/en/ecs/1.11$
Allow: /guide/en/ecs/1.4$
Allow: /guide/en/ecs/1.7$
Allow: /guide/en/ecs/1.8$
Allow: /guide/en/ecs/8.1$
Allow: /guide/en/ecs/8.11$
Allow: /guide/en/ecs/8.16$
Allow: /guide/en/ecs/8.16/index.html*
Allow: /guide/en/ecs/8.2$
Allow: /guide/en/ecs/8.6$
Allow: /guide/en/ecs/8.7$
Allow: /guide/en/elastic-stack$
Allow: /guide/en/elastic-stack-deploy/index.html*
Allow: /guide/en/elastic-stack-get-started$
Allow: /guide/en/elastic-stack-overview$
Allow: /guide/en/elastic-stack-overview/$
Allow: /guide/en/elastic-stack/$
Allow: /guide/en/elastic-stack/7.0$
Allow: /guide/en/elastic-stack/8.0$
Allow: /guide/en/elasticsearch/$
Allow: /guide/en/elasticsearch/guide$
Allow: /guide/en/elasticsearch/guide/$
Allow: /guide/en/elasticsearch/hadoop$
Allow: /guide/en/elasticsearch/hadoop/$
Allow: /guide/en/elasticsearch/painless$
Allow: /guide/en/elasticsearch/painless/$
Allow: /guide/en/elasticsearch/plugins$
Allow: /guide/en/elasticsearch/plugins/$
Allow: /guide/en/elasticsearch/plugins/6.8$
Allow: /guide/en/elasticsearch/plugins/7.10/$
Allow: /guide/en/elasticsearch/plugins/8.1$
Allow: /guide/en/elasticsearch/reference$
Allow: /guide/en/elasticsearch/reference/$
Allow: /guide/en/elasticsearch/reference/?current/mapping-fields.html%23_document_source_metadata_fields*
Allow: /guide/en/elasticsearch/reference/1.7$
Allow: /guide/en/elasticsearch/reference/6.8$
Allow: /guide/en/elasticsearch/reference/7.10/index.html*
Allow: /guide/en/elasticsearch/reference/7.13/$
Allow: /guide/en/elasticsearch/reference/8.2/$
Allow: /guide/en/elasticsearch/reference/8.4/$
Allow: /guide/en/elasticsearch/reference/8.5/$
Allow: /guide/en/enterprise-search$
Allow: /guide/en/enterprise-search-clients$
Allow: /guide/en/enterprise-search-clients/enterprise-search-node/$
Allow: /guide/en/enterprise-search-clients/enterprise-search-node/8.19$
Allow: /guide/en/enterprise-search-clients/python$
Allow: /guide/en/enterprise-search-clients/python/$
Allow: /guide/en/enterprise-search/$
Allow: /guide/en/esre/$
Allow: /guide/en/fleet$
Allow: /guide/en/fleet/$
Allow: /guide/en/fleet/7.17/index.html*
Allow: /guide/en/fleet/8.18$
Allow: /guide/en/fleet/8.18/index.html*
Allow: /guide/en/fleet/8.7$
Allow: /guide/en/graph$
Allow: /guide/en/infrastructure/guide/$
Allow: /guide/en/ingest/$
Allow: /guide/en/ingest/8.16$
Allow: /guide/en/ingest/8.18$
Allow: /guide/en/ingest/8.18/index.html*
Allow: /guide/en/ingest/8.19$
Allow: /guide/en/ingest/8.9$
Allow: /guide/en/kibana$
Allow: /guide/en/kibana/$
Allow: /guide/en/kibana/4.5$
Allow: /guide/en/kibana/4.5/$
Allow: /guide/en/kibana/5.x/_metrics_amp_axes.html*
Allow: /guide/en/kibana/5.x/graph-troubleshooting.html*
Allow: /guide/en/kibana/5.x/scripted-fields.html*
Allow: /guide/en/kibana/6.4/$
Allow: /guide/en/kibana/6.6/$
Allow: /guide/en/kibana/7.17$
Allow: /guide/en/kibana/8.1$
Allow: /guide/en/logs/guide/$
Allow: /guide/en/logs/guide/7.7$
Allow: /guide/en/logs/guide/7.9$
Allow: /guide/en/logstash$
Allow: /guide/en/logstash/$
Allow: /guide/en/logstash/2.3$
Allow: /guide/en/logstash/5.3/$
Allow: /guide/en/logstash/6.4/$
Allow: /guide/en/logstash/7.17/index.html*
Allow: /guide/en/logstash/7.6/$
Allow: /guide/en/logstash/8.10$
Allow: /guide/en/logstash/8.17/index.html*
Allow: /guide/en/logstash/8.6$
Allow: /guide/en/logstash/8.8$
Allow: /guide/en/machine-learning$
Allow: /guide/en/machine-learning/$
Allow: /guide/en/machine-learning/6.3/$
Allow: /guide/en/marvel$
Allow: /guide/en/marvel/1.3/$
Allow: /guide/en/metrics/guide/$
Allow: /guide/en/observability$
Allow: /guide/en/observability/$
Allow: /guide/en/security$
Allow: /guide/en/security/$
Allow: /guide/en/security/8.10/$
Allow: /guide/en/security/8.11/$
Allow: /guide/en/security/8.12/$
Allow: /guide/en/security/8.13/$
Allow: /guide/en/security/8.6/$
Allow: /guide/en/security/8.7/$
Allow: /guide/en/security/8.8/$
Allow: /guide/en/serverless/$
Allow: /guide/en/shield$
Allow: /guide/en/shield/$
Allow: /guide/en/siem/guide$
Allow: /guide/en/siem/guide/$
Allow: /guide/en/siem/guide/7.3$
Allow: /guide/en/starting-with-the-elasticsearch-platform-and-its-solutions$
Allow: /guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/$
Allow: /guide/en/watcher$
Allow: /guide/en/watcher/$
Allow: /guide/en/workplace-search$
Allow: /guide/en/workplace-search/$
Allow: /guide/en/workplace-search/8.8$
Allow: /guide/en/x-pack$
Allow: /guide/en/x-pack/$
Allow: /guide/en/x-pack/5.5$
Allow: /guide/en/x-pack/6.2/xpack-security.html*
Allow: /guide/en/x-pack/6.3/mapping-roles.html*
Allow: /guide/en/x-pack/6.x/actions-webhook.html*
Allow: /guide/en/x-pack/6.x/xpack-introduction.html*
Allow: /guide/jp/kibana$
Allow: /guide/server/$
Allow: /guide/cn/index.html*
Allow: /guide/en/apm/agent/*/index.html*
Allow: /guide/en/apm/get-started/7*/index.html*
Allow: /guide/en/apm/guide/index.html*
Allow: /guide/en/apm/index.html*
Allow: /guide/en/apm/server/*index.html*
Allow: /guide/en/app-search/index.html*
Allow: /guide/en/apm/agent/index.html*
Allow: /guide/en/beats/loggingplugin/index.html*
Allow: /guide/en/beats/auditbeat/index.html*
Allow: /guide/en/beats/devguide/index.html*
Allow: /guide/en/beats/filebeat/index.html*
Allow: /guide/en/beats/functionbeat/index.html*
Allow: /guide/en/beats/heartbeat/index.html*
Allow: /guide/en/beats/journalbeat/index.html*
Allow: /guide/en/beats/libbeat/index.html*
Allow: /guide/en/beats/loggingplugin/*/index.html*
Allow: /guide/en/beats/metricbeat/index.html*
Allow: /guide/en/beats/metricbeat/8.18/metricbeat-module-enterprisesearch.html*
Allow: /guide/en/beats/packetbeat/index.html*
Allow: /guide/en/beats/topbeat/index.html*
Allow: /guide/en/beats/winlogbeat/8.19/index.html*
Allow: /guide/en/beats/winlogbeat/index.html*
Allow: /guide/en/cloud-enterprise/3*/index.html*
Allow: /guide/en/cloud-enterprise/index.html*
Allow: /guide/en/cloud-on-k8s/*/index.html*
Allow: /guide/en/ecctl/*/index.html*
Allow: /guide/en/ecctl/index.html*
Allow: /guide/en/ecs-logging/index.html*
Allow: /guide/en/ecs/1.12/index.html*
Allow: /guide/en/ecs/index.html*
Allow: /guide/en/elastic-stack-get-started/index.html*
Allow: /guide/en/elastic-stack-overview/index.html*
Allow: /guide/en/elastic-stack/7.17/index.html*
Allow: /guide/en/elastic-stack/index.html*
Allow: /guide/en/elasticsearch/client/curator/*index.html*
Allow: /guide/en/elasticsearch/client/curator/index.html*
Allow: /guide/en/elasticsearch/client/go-api/index.html*
Allow: /guide/en/elasticsearch/client/groovy-api/index.html*
Allow: /guide/en/elasticsearch/client/java-api-client/index.html*
Allow: /guide/en/elasticsearch/client/java-api/6.8*index.html*
Allow: /guide/en/elasticsearch/client/java-rest/6.8/*index.html*
Allow: /guide/en/elasticsearch/client/java-rest/7.17/index.html*
Allow: /guide/en/elasticsearch/client/javascript-api/index.html*
Allow: /guide/en/elasticsearch/client/net-api/8.19/index.html*
Allow: /guide/en/elasticsearch/client/net-api/index.html*
All
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 846 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
342 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
75 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
152 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
742 ms
Total Time Total request time from DNS lookup through full response.
847 ms

Connection waterfall

DNS Lookup 342 ms TCP Connect 75 ms TLS Handshake 152 ms Server Processing 173 ms Content Transfer 105 ms
B
TLS Certificate Expiry & Recommendations
252 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

252
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.elastic.co

https://www.elastic.co

645 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.elastic.co200645 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (75 ms)
PASS
IPv6 reachable (75 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42:12::729
Got: 75 ms connect
IPv6 Ready
AAAA Records 2a04:4e42:12::729 Connection Reachable (75 ms)
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.elastic.co/
301https://elastic.co/

Preferred variant: www

HTTP → HTTPS

301http://www.elastic.co/ → https://www.elastic.co/

Consistent

A+
Domain Intelligence
elastic.co — via GoDaddy.com, LLC, 15 years, 11 months old
PASS
elastic.co — via GoDaddy.com, LLC, 15 years, 11 months old
Info::
Domain registered until Jul 19, 2026 (3 months remaining)
Info::
Registrar: GoDaddy.com, LLC
Domain expiry

34 days

July 19, 2026

SSL certificate

252 days

Issued by GlobalSign nv-sa

Domain age

15 years, 11 months

Registered July 20, 2010

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2600:1901:0:1f6d::

Registrar

GoDaddy.com, LLC

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar GoDaddy.com, LLC
Created July 20, 2010 (15 years, 11 months ago)
Expires July 19, 2026 (3 months)
Last Updated October 7, 2025
Name Servers ns-339.awsdns-42.com, ns-785.awsdns-34.net, ns-1737.awsdns-25.co.uk, ns-1168.awsdns-18.org
Registrant Domains By Proxy, LLC
Hosting
IP Address 2600:1901:0:1f6d::
Data source: whois (4.8s)
A+
CDN & Delivery
Fastly (HIT, MISS)
PASS
Fastly (HIT, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-bfi-kbfi7400103-BFI, cache-nrt-rjaa8190073-NRT
Info::
CDN cache status: HIT, MISS
CDN Detected: Fastly
Provider Fastly Cache Status HIT, MISS Evidence x-served-by: cache-bfi-kbfi7400103-BFI, cache-nrt-rjaa8190073-NRT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback