◈ OORTYEET VERIFY
VERIFICATION WORKSPACE / EMAIL AUTHENTICATION

Know when your email protection changes.

Schedule public DNS observations, review recorded evidence, receive optional alerts, and analyze DMARC aggregate XML you upload. Your existing VERIFY account and subscription power everything.

Checking account…
—Active monitors
—Changes in 30 days
—Imported DMARC reports
—Reported alignment*

Scheduled monitoring

Our read-only checks cover MX, SPF, DMARC, TLS-RPT, and an optional DKIM selector. Initial snapshots are baselines; subsequent differences create alerts.

Paid plan required. Monitoring checks public declarations only; they cannot prove email delivery or detect every authentication failure.

Monitors & signed observations

Your active monitoring rules will appear here.

Domain authorization for DMARC reports

To import DMARC aggregate data, first demonstrate control of your sending domain with a DNS TXT challenge.

DNS control is point-in-time; it doesn't authenticate an uploaded report's claimed sender.

DMARC aggregate reports

Import a DMARC XML report provided by your mail receiver. The report remains customer-supplied, not independently authenticated. No access to anyone's inbox is required.

Export my DMARC summary CSV ↗

Alerts and changes

Only verified differences after an initial baseline generate change alerts. Email delivery is retried and may be delayed during provider outages.

What our evidence actually proves

Each scheduled observation is stored with UTC timing, the DNS resolver name, exact observed values, a SHA-256 digest, and a server-held HMAC-signed downloadable receipt. You can validate issuance through VERIFY. These receipts do not prove a physical task, mail delivery, the authenticity of user-uploaded XML, or regulatory compliance.

OORTCORE receives only pseudonymous event references and receipt hashes. OORTSERV's bookings and OORTBOT's simulations remain independent, with their original functionality preserved.