The same passport built to stop spoofed calls also gives networks a way to tell whethers it is a from a verified sender or from an anonymous automated one — before that traffic ever reaches you.
Automated senders — AI-driven call bots, message bots, and content-generating accounts — currently look identical to legitimate traffic at the network level. There's no equivalent of a "return address" that a receiver, ISP, or platform can check before deciding whether to let a bot-originated message or an actual call coming through. A Sender Passport certificate closes that gap by attaching a verifiable, revocable identity claim to the senders data, and by requiring that claim to verifed by enduser whether the sender is legtimate or not.
Every outbound call, message, or data request carries a passport issued through the global CA hierarchy and an ISP sub-CA, including a disclosed attestation of whether the sender is legimate, a verified business system, or a bot that is not.
The Internet Service Provider-issued equipmnet (modem, cellular gateway, cable box) checks the passport trust tier and revocation status centrally, the same way it would for any sender — no extra hardware required in the home.
Automated traffic that fails to disclose itself as a bot, or that presents no valid certificate at all, is treated the same as spoofed traffic under the fail-closed model — flagged, deprioritized, or dropped depending on the trust tier the receiver has chosen.
A bot certificate that crosses the abuse threshold — spam volume, fraud complaints, scraping violations — gets added to the shared cross-ISP revoked-sender database, so it's blocked everywhere at once rather than ISP by ISP.
This builds directly on the STIR-SHAKEN-style attestation and revocation model already proposed for calls and messages — extending trust-tier attestation to explicitly cover disclosed automated senders. Get involved or read the full technical framework.
Read the problem statement Support this work