<img src=x onerror=alert("xssprobe1788176000")> Motors 1788176000 › Verification

What this proves, precisely. X-Protocols checked who is behind
<img src=x onerror=alert("xssprobe1788176000")> Motors 1788176000 before publishing anything, and every record it publishes
is signed with a private key only this platform holds on the publisher's
behalf. It does not prove the published facts are true — it proves who
published them and that they were not altered after signing. What was
actually checked is below.
How this was proven
| Status | verified |
| Trust tier | identity_verified |
| Domain | none on file |
| Evidence accepted | postal_challenge — xss_e2e fixture: someone receiving mail there acted on it registry_record — xss_e2e fixture: a company of this name is registered |
This business was verified without proving a domain. That is a
full verification, not a lesser one: the evidence above was reviewed by a person before anything
was published, and the records are served on exactly the same terms. It is stated separately from
the domain because they are two different facts, and a page that merged them would be claiming
something nobody checked.
Cryptographic proof
Every response this publisher's data appears in can carry an Ed25519 signature.
An agent — or anyone — can verify one without trusting this platform at all:
Embed this badge
Publishers may place this on their own site, linking back here:
<a href="https://x-protocols.com/b/img-srcx-onerroralertxssprobe1788176000-motors-1788176000/verify" rel="nofollow noopener"><img src="https://x-protocols.com/b/img-srcx-onerroralertxssprobe1788176000-motors-1788176000/badge.svg" alt="AI Optimized & Verified by X-Protocols" width="240" height="28"></a>