No CMS or framework detected, hosted on Render behind Cloudflare. Domain registered in 2026.
chronoverify.com is hosted on Render behind Cloudflare. It measures traffic with Cloudflare Web Analytics. It sends email through Amazon SES.
| Technology | Version | First seen |
|---|---|---|
| CDN & Hosting2 | ||
| – | 9 Nov 2026 | |
| – | 9 Nov 2026 | |
| Analytics & Tag Management1 | ||
| – | 9 Nov 2026 | |
| Transactional Email2 | ||
| – | 9 Nov 2026 | |
| Fonts & Icon Fonts1 | ||
| – | 9 Nov 2026 | |
Registration from the registry's RDAP record, the certificate the site serves, and its rank in public traffic lists.
The crew hasn’t read this site’s colors yet. We read a palette when we capture a site’s screenshot, busiest sites first. Meanwhile, browse palettes from other sites.
From what the site says about itself, and account IDs it shares with other sites.
route3.mx.cloudflare.netroute2.mx.cloudflare.netroute1.mx.cloudflare.nettricia.ns.cloudflare.comleonard.ns.cloudflare.comv=spf1 include:_spf.mx.cloudflare.net ~allsmithery-verification=0d7acdfe3c2601feb7742fe9f46f83db5419e4a2390565c24f200e048891b957google-site-verification=5apwZJetp87jtSvwUWRH1Xc2pdE2_LDCcJNe00YA1mIv=DMARC1; p=none; rua=mailto:parkmail-dmarc@dynadot.comUser-agent: * Allow: / User-agent: GPTBot Allow: / User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: ClaudeBot Allow: / User-agent: Claude-User Allow: / User-agent: Claude-SearchBot Allow: / User-agent: PerplexityBot Allow: / User-agent: Perplexity-User Allow: / User-agent: Google-Extended Allow: / User-agent: Applebot Allow: / User-agent: Applebot-Extended Allow: / User-agent: CCBot Allow: / User-agent: cohere-ai Allow: / User-agent: Bytespider Allow: / User-agent: Amazonbot Allow: / User-agent: Amzn-SearchBot Allow: / User-agent: Amzn-User Allow: / User-agent: Meta-ExternalAgent Allow: / User-agent: Meta-WebIndexer Allow: / User-agent: Meta-ExternalFetcher Allow: / User-agent: MistralAI-User Allow: / User-agent: MistralAI-Index Allow: / User-agent: MistralAI-Training Allow: / User-agent: DuckAssistBot Allow: / User-agent: YouBot Allow: / Sitemap: https://chronoverify.com/sitemap.xml # AI guide: https://chronoverify.com/llms.txt
# ChronoVerify
> ChronoVerify checks when a photo was taken and whether it shows signs of editing. It reads capture time and provenance from EXIF and XMP, cryptographically validates C2PA Content Credentials against the official C2PA and CAI trust lists, runs classical pixel forensics, and returns one plain-language verdict with a confidence score. It works on any image, signed or not, through a free web tool and a developer API.
ChronoVerify is provenance-first, not a deepfake classifier. Verdicts are investigative triage with a stated confidence. The integrity layer (file hash and signature) is cryptographic and reproducible; the verdict layer is probabilistic and labeled as such. Built by a veteran intelligence analyst.
## Core pages
- [Free verifier](https://chronoverify.com/): Upload or paste an image and get a verdict in seconds.
- [Developer docs](https://chronoverify.com/docs): First verdict in under a minute with one keyless curl, the five-verdict decision table for pipelines, production limits and errors, and links to every SDK and machine-readable spec.
- [Method and limits](https://chronoverify.com/method): How the deterministic pipeline works and what it can and cannot tell you.
- [Pricing and API access](https://chronoverify.com/pricing): Free tier, pay as you go, and one flat monthly plan.
- [How ChronoVerify compares](https://chronoverify.com/compare): Design choices by category, with common questions, plus named head-to-head comparisons vs Truepic, Sightengine, and Hive.
- [Compliance and Article 50](https://chronoverify.com/compliance): C2PA validation and a signed, timestamped audit record as a verification and audit layer for EU AI Act Article 50 transparency (in application since August 2, 2026).
- [C2PA Conforming Products List, with ChronoVerify's record](https://chronoverify.com/c2pa-conformance): every validator product on the list, the one command that checks any record against the C2PA's public register, and ChronoVerify's record in full. The C2PA publishes no per-record pages, so this is the citable page for a record.
- [Benchmark and calibration](https://chronoverify.com/benchmark): Measured on real photos: no authentic capture in the corpus wrongly flagged, and no known edited derivative cleared as authentic (most read inconclusive by design). Plus the forensic-resolution decision.
- [Sample images](https://chronoverify.com/demo): Six sample files with known ground truth that demonstrate each verdict, safe to test the verifier, the API, or the browser extension against.
- [Contact](https://chronoverify.com/contact): Write to the operator: a question, a bug, a verdict that looks wrong, or a partnership. Agents can POST https://chronoverify.com/v1/contact with JSON fields message (required), email, and name; no key needed.
## Integrations and agent tools
- [Integrations hub](https://chronoverify.com/integrations): Wire ChronoVerify into your agent, framework, or workflow.
- [MCP server](https://chronoverify.com/mcp): One-click install for Claude, Cursor, and VS Code (npm chronoverify-mcp). Tools: verify_image (typed verdict) and get_signed_report (signed PDF audit record). A hosted (remote) MCP endpoint is also live at https://chronoverify.com/mcp/http (streamable HTTP, keyless, read-only verify_image); MCP clients can auto-discover it from https://chronoverify.com/.well-known/mcp.json.
- [OpenAI function calling](https://chronoverify.com/integrations/openai) and [Claude tool use](https://chronoverify.com/integrations/anthropic): copy-paste tool definitions for the OpenAI Chat Completions and Responses APIs and the Anthropic Messages API.
- [LangChain](https://chronoverify.com/integrations/langchain), [LlamaIndex](https://chronoverify.com/integrations/llamaindex), and [CrewAI](https://chronoverify.com/integrations/crewai): load the MCP server as native framework tools.
- [n8n](https://chronoverify.com/integrations/n8n) and [REST and webhooks](https://chronoverify.com/integrations/rest): one HTTP call from any workflow or language; first-party Python and TypeScript SDKs.
## Glossary and use cases
- [Glossary](https://chronoverify.com/glossary): plain-language definitions of C2PA, Content Credentials, EXIF, XMP, provenance, capture time, error level analysis, the C2PA trust list, EU AI Act Article 50, the SHA-256 content fingerprint, geolocation, chronolocation, and reverse image search.
- [Use cases](https://chronoverify.com/use-cases): how teams apply capture-time and provenance verification by vertical, with the workflow, which verdicts matter, and the limits for [insurance claims](https://chronoverify.com/use-cases/insurance), [newsrooms](https://chronoverify.com/use-cases/newsroom), [marketplaces](https://chronoverify.com/use-cases/marketplace), [trust and safety](https://chronoverify.com/use-cases/trust-and-safety), [KYC and onboarding](https://chronoverify.com/use-cases/kyc), [gig and field work](https://chronoverify.com/use-cases/gig-work), and [OSINT and investigations](https://chronoverify.com/use-cases/osint).
- [Image OSINT toolbox](https://chronoverify.com/resources): curated, liveness-checked external tools for the other half of image verification (reverse image search, geolocation, chronolocation, pixel forensics, archives), with notes on what each can and cannot tell you. ChronoVerify covers the internal-evidence half; these cover context no file carries.
## Free tools
- [Free tools](https://chronoverify.com/tools): standalone, no-signup utilities, each separately usable. [SHA-256 and SHA-512 hash checker](https://chronoverify.com/tools/hash) computes a file content fingerprint entirely in your browser, so the file never leaves your device. [EXIF and XMP viewer](https://chronoverify.com/tools/exif) shows the raw metadata written in a photo (capture time, device, GPS, software tags); metadata can be edited, so it shows what is written, not whether it is true. [C2PA inspector](https://chronoverify.com/tools/c2pa) reads and cryptographically validates Content Credentials against the official C2PA and CAI trust lists. [EU AI Act Article 50 marking checker](https://chronoverify.com/tools/article-50) checks an image for machine-readable AI-provenance marking (validated C2PA Content Credentials and the IPTC digital source type declaration); absence of marking is not evidence either way. [Signed report verifier](https://chronoverify.com/tools/report) checks that a ChronoVerify PDF report carries a valid ChronoVerify signature over the exact file it describes; it confirms the report is genuine and unaltered, it does not re-assess the photo.
## Downloadable packs
- [Packs catalog](https://chronoverify.com/packs): six downloadable packs by the analyst who built ChronoVerify, sold at store.chronoverify.com: OSINT research agents for Claude Code ($29), an ffmpeg render cookbook ($12), an MCP publishing runbook ($12), free image provenance recipes, a pay-what-you-want OSINT prompt pack, and a $39 bundle of all five. Plain Markdown files; one purchase covers a whole organization.
- [Verify before you cite](https://chronoverify.com/verify-before-you-cite): the on-site method page. Answer where an image came from and whether it has changed since, before citing it, in four free steps: one keyless verify, reading the verdict, a free key (100 checks per month), and the downloadable recipes pack. It does not detect AI images or deepfakes.
- [osint-verifier on GitHub](https://github.com/beeswaxpat/osint-verifier): a free, MIT-licensed OSINT source-verification subagent for Claude Code from the flagship pack: Admiralty source grading, single-source and uncited-claim flags, and circular-reporting checks.
## API
- Verify: POST https://chronoverify.com/v1/verify with a multipart `file`, or a form field `url`. For metered API use send `Authorization: Bearer cv_live_...`; with no header it runs the free, rate-limited public path. Example: `curl -X POST https://chronoverify.com/v1/verify -H "Authorization: Bearer cv_live_..." -F "file=@photo.jpg"`
- Response: a JSON object, for example {"verdict": "consistent", "confidence": 61, "capture_time": {"value": "2026-05-18T14:32:10", "source": "exif"}, "c2pa": {"present": false}, "integrity": {"sha256": "..."}}. Full field reference and language examples: https://chronoverify.com/method#api
- Response JSON Schema: GET https://chronoverify.com/v1/verify.schema.json is a versioned JSON Schema of the verify response (verdict enum, signal directions, the C2PA block, integrity fingerprints), for agents and codegen.
- Signing key: GET https://chronoverify.com/v1/key returns the Ed25519 public key used to sign PDF reports.
- Verdict fields: capture_time, capture_location, capture_device, c2pa, metadata_consistency, pixel_forensics, integrity (SHA-256 and SHA-512), and one verdict enum: provenance_confirmed, consistent, inconclusive, metadata_anomaly, or manipulation_indicated.
- Shareable verdict links: add form field `permalink=true` to POST https://chronoverify.com/v1/verify to also store the verdict (never the image) and get back an unlisted link in the response's permalink field, viewable by humans at /v/{id} and as raw JSON at /v/{id}.json. Off by default; nothing is stored unless the caller opts in. API-key links do not expire; keyless links expire after 90 days.
- Pricing: free 100 per month; pay as you go $0.003 per image; Scale $299 for 200,000 per month with signed, timestamped PDF reports included in the quota. No operation multipliers, no sales call. Signed PDF audit reports (POST /v1/report) are a premium unit at $2.00 each. On pay as you go each report draws $2.00 from the prepaid balance from the first one: a key's free monthly allotment covers verifications only. On a monthly subscription reports come out of the plan's included quota instead.
- Single signed report, no key: a one-time signed PDF report for one photo is $29, bought by a human at the verdict screen of the free verifier at https://chronoverify.com/ after uploading the photo there. Same PDF as the API report; the $29 covers a single no-account, no-integration purchase. Sample: https://chronoverify.com/static/sample-signed-report.pdf
## For AI agents: onboarding in four steps
1. Try it with no key or signup: `curl -X POST https://chronoverify.com/v1/verify -F "url=https://chronoverify.com/samples/sample_camera.jpg"` (free, per-IP rate limited). Or connect the hosted MCP endpoint at https://chronoverify.com/mcp/http.
2. Read the machine contract: GET https://chronoverify.com/v1/onboarding returns one JSON manifest with the auth scheme, pricing, quota headers, error semantics, and every endpoint. GET https://chronoverify.com/openapi.json and GET https://chronoverify.com/v1/verify.schema.json cover codegen.
3. Get your own free key, no card and no human step: POST https://chronoverify.com/v1/keys/free with an `email` field (form or JSON). It grants 100 verifications per month, one key per email, shown once in the response. Signed PDF reports and volume beyond the free 100 need a paid key: ask your user to open https://chronoverify.com/pricing and buy prepaid credits ($5 minimum) or a plan; that key is revealed after checkout and at https://chronoverify.com/dashboard.
4. Send `Authorization: Bearer cv_live_...` and watch the X-Credits-Remaining-USD and X-Quota-Remaining response headers to know when to tell your user to top up. Out of credit returns HTTP 402 with a plain-language detail.
## C2PA conformance
ChronoVerify is listed on the C2PA Conforming Products List as a **conformant validator product**, record `019f8a20-6452-7a43-b11b-59d0b0e4a84a`, specification version 2.2, conformance program version 0.1. The listing covers VALIDATION of `image/jpeg`, `image/png`, `image/webp` and `image/avif`. It does not cover generation: ChronoVerify reads and validates Content Credentials, it does not sign or mint them. Verify the record independently in the [C2PA Conformance Explorer](https://spec.c2pa.org/conformance-explorer/) or in the [public list JSON](https://github.com/c2pa-org/conformance-public/blob/main/conforming-products/conforming-products-list.json). The C2PA operates a conformance program and does not certify: this is not a certification, an audit, or an endorsement, and it is not an EU AI Act certification, which does not exist.
As of August 3, 2026, the Conforming Products List held 152 records, of which 20 are validator products from 18 distinct vendors; the rest are generator products that create Content Credentials rather than read them. 6 validator products declare US as the country in their product Distinguished Name and also declare image containers, and ChronoVerify is the 6th of those by conformance date and by earliest public disclosure date. Those counts are a dated snapshot of a register that re-syncs several times a day: cite the date with the number. The record, the full validator table, and the one command that checks it are at [https://chronoverify.com/c2pa-conformance](https://chronoverify.com/c2pa-conformance).
## Good for
- Verifying capture time and provenance of any photo, signed or not
- Triage at scale for insurance claims, marketplaces, dating apps, fintech identity checks, gig platforms, and newsrooms
- Reading C2PA Content Credentials and EXIF or XMP, with a graceful result when none are present
- Flagging locally edited or spliced regions on unsigned images with classical pixel forensics (block-level error-level analysis, noise dispersion), surfaced as triage signals for human review, not proof and not AI detection
## Not for
- Detecting deepfakes or AI-generated images
- Proving a photo is authentic, or being the only basis for an automated decision
- Copy-move (clone) detection: the pixel layer is block-level error-level analysis and noise dispersion, documented at https://chronoverify.com/method; it does not include copy-move forensics
- Drafting legal or governance documentation, such as EU AI Act Annex IV technical packs: ChronoVerify produces the signed audit records a compliance file cites, not the file itself
## How ChronoVerify compares
- Works on any image, signed or not. It reads C2PA Content Credentials when present and falls back to EXIF, XMP, and pixel forensics when they are absent, instead of only validating already-signed files.
- Flat, self-serve pricing: $0.003 per image with no per-operation multipliers, no minimum seat, and no sales call. Start on the free tier and add prepaid credits without talking to anyone.
- Provenance-first by design. Verdicts are investigative triage with a stated confidence and documented limits, not a black-box authenticity score.
- One plain-language verdict (provenance_confirmed, consistent, inconclusive, metadata_anomaly, manipulation_indicated) plus a 0 to 100 confidence, the same object in the browser and the API.
- Named head-to-head comparisons, with every competitor claim sourced to that vendor's own public pages and dated: [ChronoVerify vs Truepic](https://chronoverify.com/compare/truepic) (Truepic signs media at capture; ChronoVerify validates provenance on any image, self-serve), [ChronoVerify vs Sightengine](https://chronoverify.com/compare/sightengine) (Sightengine scores AI-generated and deepfake likelihood; ChronoVerify validates C2PA provenance and capture time), and [ChronoVerify vs Hive](https://chronoverify.com/compare/hive) (Hive scores AI-generated and deepfake content; ChronoVerify validates C2PA provenance with a signed, timestamped audit record).
## Guides
- [What a C2PA signature covers, and how one ended up covering nothing](https://chronoverify.com/blog/what-a-c2pa-signature-covers): A C2PA data hash (c2pa.hash.data) covers the file minus byte-range exclusions, which exist so the manifest can sit inside the file it describes. A signer can write one exclusion over the whole file, so the hash is taken over zero bytes and the signature covers nothing about the picture (David Buchanan, October 2, 2026). C2PA 2.2 section 15.12.1.1 tells validators to reject that with assertion.dataHash.mismatch; c2pa-rs rejects it from 0.91.0 (September 21, 2026). ChronoVerify ran c2pa-rs 0.89, reproduced the problem against its own validator, and since October 14, 2026 reads any exclusion that reaches into the picture data as Invalid with assertion.dataHash.mismatch. Checked against 209 sample files under four trust lists before shipping; only the two attack files changed.
- [How to prove when a photo was taken, for an insurance claim or a dispute](https://chronoverify.com/blog/how-to-prove-when-a-photo-was-taken): For the person who has to show an adjuster, a landlord, a marketplace, an employer, or a lawyer when a photo was taken. A screenshot of the photo's properties proves nothing because the date is a text field anyone can retype. What holds up better, in order: the original file rather than a screenshot or a messaging-app copy; the dates inside it agreeing with each other; a Trusted C2PA Content Credential; and a third-party signed record of what the file contains. The $29 single-photo report (no account, bought at the free verifier's result screen) records the SHA-256, every date read, each check and its outcome, the credential result, and the pixel analysis, signed with Ed25519 and carrying an RFC 3161 trusted timestamp, checkable at https://chronoverify.com/tools/report or offline. It is a record of what the file says, not proof that the scene happened, and ChronoVerify does not say whether any insurer, platform, or court accepts it.
- [How to tell if the date or time on a photo was changed](https://chronoverify.com/blog/how-to-tell-if-a-photo-date-was-changed): No field in a photo says its date was edited; the check is whether the clocks the file carries agree. EXIF DateTimeOriginal, DateTimeDigitized, DateTime (last save), the GPS UTC stamps, and the filesystem dates, who writes each, and the contradictions that show a rewrite (last save earlier than capture by over an hour, capture time more than 48 hours in the future or before 1990, original and digitized split, GPS clock not a whole time zone from local time). A later save time and an editor Software tag are reported neutrally. ExifTool can rewrite every field consistently, so agreement is not proof; a Trusted C2PA credential and outside evidence are the durable anchors. Signed single-photo report at $29, no account.
- [The C2PA Trust List, explained](https://chronoverify.com/blog/c2pa-trust-list-explained): The Trust List (who may sign; anchors whose signers reach the Trusted state) versus the Conforming Products List (which products were checked), what Trusted, Valid, and Invalid mean, dated anchor counts (57 signer + 22 TSA certificates as of 2026-08-22), and how ChronoVerify's weekly refresh validates and ships. Only Trusted maps to validated provenance.
- [What AI-presented images actually carry: 73 images, 38 companies, August 2026](https://chronoverify.com/blog/what-ai-images-actually-carry): A dated sweep of the marking layer as delivered. 73 images that 38 companies publicly present as AI-generated or AI-altered, fetched exactly as each company's own page delivers them and checked with POST /v1/verify on August 3, 2026: 72 carried no C2PA Content Credentials at all, and 1 arrived with a validated credential (Flipsnack's AI demo image, signed by OpenAI Media Service, software agent gpt-image, permanent record https://chronoverify.com/v/T70rPUIsInISOOB4). Absence of a credential is not evidence an image is fake; most credential loss is mechanical (optimizers and CDN re-encodes). Category breakdown, method, and row-level evidence for journalists on request.
- [ChronoVerify joins Google, Microsoft, Meta, and OpenAI as initial signatories of the EU Code of Practice on Transparency of AI-Generated Content](https://chronoverify.com/blog/chronoverify-eu-code-of-practice-signatory): The announcement of record for the signatory listing. The European AI Office published the first list of signatories on July 31, 2026: about 19Contact: mailto:support@chronoverify.com Expires: 2027-11-09T03:02:16Z Preferred-Languages: en Canonical: https://chronoverify.com/.well-known/security.txt Policy: https://chronoverify.com/security # Put SECURITY or CONFORMANCE in the subject line. # CONFORMANCE covers any case where ChronoVerify's C2PA validation # result disagrees with the Content Credentials specification. # Good-faith research is authorised; see the policy URL above.
| – |
| 9 Nov 2026 |