Skip to content
https://prometheus.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 3 REVIEW
B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1248 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 1248 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a content-signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a content-signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a content signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via content signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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 (REVALIDATED)
REVIEW
Cloudflare (REVALIDATED)
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9e8bc6627eec5e4b-EWR
Info::
CDN cache status: REVALIDATED
CDN Detected: Cloudflare
Provider Cloudflare Cache Status REVALIDATED Evidence cf-ray: 9e8bc6627eec5e4b-EWR
A+
DNS Records
2 A records, 71 ms lookup
PASS
2 A records, 71 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.201.240, 104.21.60.220
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3030::6815:3cdc, 2606:4700:3030::ac43:c9f0
Info::
2 nameserver(s) configured
Got: damon.ns.cloudflare.com, gene.ns.cloudflare.com
Info::
6 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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 71 ms
Got: 71 ms
A172.67.201.240, 104.21.60.220
AAAA2606:4700:3030::6815:3cdc, 2606:4700:3030::ac43:c9f0
CNAME
NSdamon.ns.cloudflare.com, gene.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
15 bq2ktxwtt2jn3bfqdxyun7k5xiocls2bzyovljf6x3phdcvxr56q.mx-verification.google.com
TXT
google-site-verification=pD7ffQ-fdaKAyzu2JGGbJ6s_vo4sbxFA-F7EbiAqai0
CAALookup not available with standard resolver
Resolved in 71 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.

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)

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://prometheus.io

https://prometheus.io

38 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://prometheus.io20038 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3030::6815:3cdc, 2606:4700:3030::ac43:c9f0
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:3030::6815:3cdc, 2606:4700:3030::ac43:c9f0 Connection Reachable (2 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: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.prometheus.io/
200https://prometheus.io/

Preferred variant: non-www

HTTP → HTTPS

301http://prometheus.io/ https://prometheus.io/

Consistent

A+
Domain Intelligence
prometheus.io — via 1API GmbH, 13 years, 4 months old
PASS
prometheus.io — via 1API GmbH, 13 years, 4 months old
Info::
Domain registered until Jan 25, 2027 (9 months remaining)
Info::
Registrar: 1API GmbH
Domain expiry

226 days

January 25, 2027

SSL certificate

87 days

Issued by Google Trust Services

Domain age

13 years, 4 months

Registered January 25, 2013

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3030::6815:3cdc

Registrar

1API GmbH

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar 1API GmbH
Created January 25, 2013 (13 years, 4 months ago)
Expires January 25, 2027 (9 months)
Last Updated January 25, 2026
Name Servers gene.ns.cloudflare.com, damon.ns.cloudflare.com
Registrant The Linux Foundation
Hosting
IP Address 2606:4700:3030::6815:3cdc
Data source: whois (0.5s)
A+
HTTP Probe Timing
Total 43 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
43 ms
Total Time Total request time from DNS lookup through full response.
44 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 2 ms TLS Handshake 10 ms Server Processing 26 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback