GET lencr.org HTTP 200116 ms2.6 KB$0.000061 captured Aug 7, 2026
lencr.org, as data
One API turns any lencr.org page into markdown, structured JSON, its link graph or a screenshot, and crawls the whole site the same way. The panel shows the real response we captured.
- Render mode
- Plain HTTP, no browser needed
- Response
- HTTP 200 in 116 ms
- Page size
- 2.6 KB of markdown, 39 lines
- Fields
- Business Name, Address, Phone, Category and 2 more
- Captured
- Aug 7, 2026
Free balance on signup, no card. This lencr.org page cost $0.000061 to fetch.
# lencr.orgNo, the data on `lencr.org` is never malicious. When a device connects to`lencr.org`, it’s because client software on that device (like a web browser oran app) connected to another site, saw a Let’s Encrypt certificate, and istrying to verify that it’s valid. This is routine for many clients.We can’t speak to whether the *other site* being connected to is malicious. Ifyou’re investigating network activity that seems unusual, then you may want tofocus on the connection that started just before the connection to `lencr.org`.The pattern of clients’ connections to `lencr.org` might look unusual orintermittent. Clients might never retrieve this data; only retrieve subsets ofit; or “cache” some data for efficiency, so they’ll only access it sometimes(the first time they need it, and when the data may have expired).# What exactly is this data for?When client software (like a web browser or an app) connects to a site, and thatsite presents a certificate, the client should verify that the certificate isauthentic and valid. This data helps clients do that in several ways.* Under `c.lencr.org`, we provide Certificate Revocation Lists (CRLs) listingall the unexpired certificates that we issued and later revoked.* Under `i.lencr.org`, we provide copies of our intermediate “issuer”certificates, which are either signed by one of our root certificates or“cross-signed” by another Certificate Authority (CA). A client may use thisdata to confirm the “chain of trust” from the end-entity certificate it’sverifying, via one or more intermediate steps, to a root CA certificate that it# Why “`lencr.org`”?We used to use longer URLs like `http://example.int-x3.letsencrypt.org/`. However,when we issued our new root and intermediate certificates, we wanted tomake them as small as possible. Every HTTPS connection on the web (billions perWhat Spider does on lencr.org
Same key, five endpoints. The numbers under a cell were measured on this page.
Page to markdown
Clean text for RAG and LLM context, boilerplate removed. The lane that runs without a key.
116 ms · $0.000061Page to JSON
Spider reads the page and names the fields. Pass your own schema when you need exact keys.
Rendered capture
Real Chromium, full-page PNG. The same call also returns the rendered HTML.
The call behind the panel
This request produced the response above. Paste it with your key and you get the same bytes.
curl -X POST https://api.spider.cloud/scrape \
-H "Authorization: Bearer $SPIDER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://lencr.org/", "return_format": "markdown"}'from spider import Spider
app = Spider()
params = {"return_format": "markdown"}
page = app.scrape_url("https://lencr.org/", params=params)
print(page[0]["content"])import { Spider } from "@spider-cloud/spider-client";
const app = new Spider();
const [page] = await app.scrapeUrl("https://lencr.org/", {
return_format: "markdown",
});
console.log(page.content);What lencr.org costs
Multiplied from the measured 2.6 KB page. Estimates round to the cent.
1 GB of transfer costs $1, plus $0.001 per CPU minute, and failed requests cost $0. Crawling daily? The Unlimited plan is a flat monthly rate.
Point this at the rest of lencr.org.
The capture above took 116 ms and cost $0.000061. The same call takes any URL on lencr.org.