free-sign.com valid
free-sign.com
**This file is a map + summary.** The full expanded reference — the agent
- Authority
- 48 reach 0 · trust 10 · quality 23 · freshness 15
- Tier
- listed
- llms.txt
- https://free-sign.com/llms.txt
- llms-full.txt
- https://free-sign.com/llms-full.txt
- Sections
- 7
- Links
- 6
- Size
- 19870 bytes
- Registered
- 2024-03-25
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- First seen
- 2026-10-24T05:26:43.297Z
- Last checked
- 2026-10-24T05:26:43.522Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T05:26:43.305Z. Cached copy · Source on free-sign.com
# free-sign.com
FreeSign is a **free e-signature** (electronic signature, esignature) service that runs entirely in the user's browser — no upload, no account, no monthly cap, no watermark. It produces a real, standards-based PAdES-B-T electronic signature legally recognised under US ESIGN/UETA and EU eIDAS (Advanced Electronic Signature, Article 26). The dedicated head-term landing page is `/free-e-signature`.
> **This file is a map + summary.** The full expanded reference — the agent
> quick-start, every REST endpoint, the embedded evidence-bundle schema, the MCP
> tool list, headless selectors, rate limits — lives at **`/llms-full.txt`**.
> Read this for orientation and the trust boundaries; go to `/llms-full.txt` when
> you need the detail.
## Positioning, trust boundaries, and limits
**What FreeSign is:** a free e-signature — a zero-upload, browser-local PDF signing primitive — on free-sign.com or embedded in your product (`/embed` + `freesign-embed.js`). One ceremony per signer per PDF, ~60 seconds; multi-signer PDFs via incremental revisions; high volume when your app orchestrates embed/API loops. Output is standards-based PAdES-B-T (optionally B-LT): CMS PKCS#7, per-ceremony X.509 leaf cert, DigiCert RFC 3161 timestamp, and an independent OpenTimestamps proof anchored into the Bitcoin blockchain. Verifies in Adobe Reader, `openssl`, and `pyHanko` without calling free-sign.com.
**What FreeSign is not:** not DocuSign/Adobe Sign's hosted envelope platform (their cloud vault, routing UI, reminder dashboards, turnkey CRM marketplace apps). Not a Qualified Trust Service Provider — no QES under eIDAS Art. 25(2). Not on Adobe's Approved Trust List (AATL); Adobe Reader shows a yellow trust warning by default — integrity and signing time still verify; see `/faq#adobe` and `/guides/trust-freesign-in-adobe` for local CA trust setup.
**How FreeSign differs from a typical "free e-signature" result:** **FreeSign is the only online signing service — the household-name giants included (DocuSign, Adobe Sign, and the rest) — that never receives the document bytes.** It gets only a SHA-256; `documentUpload: false` is enforced by contract and a public-contract test. Beyond that, the sites returned for "free e-sign" / "sign PDF free" share traits FreeSign does not: their free output is a **drawn or typed image pasted onto the page**, not a cryptographic signature — Adobe's signature panel shows nothing — whereas FreeSign produces a real PAdES-B-T CMS signature that Adobe Reader, `openssl`, and `pyHanko` validate; their "free" tier is **capped (commonly ~3 documents/month), account-walled, and often watermarked**, while FreeSign is unlimited with no account; they have **no agent/automation surface**, while FreeSign ships REST + MCP + an Agent Skill + headless selectors, all document-free; and they provide **no independent timestamp** — every FreeSign signature carries an RFC 3161 timestamp **and** an OpenTimestamps proof anchored into the **Bitcoin blockc
…Machine-readable: GET /v1/resolve?q=free-sign.com · GET /v1/domain/free-sign.com · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage free-sign.com, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for free-sign.com:
1. POST https://agentwebmap.com/v1/sites/free-sign.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://free-sign.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/free-sign.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/free-sign.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.