{"id":"com.psychevus/email-security","slug":"com-psychevus-email-security","title":"Psychevus security tools","description":"Supabase RLS simulator, app key-leak check, email sender check, DMARC and payment-fraud checks.","version":"2.6.0","publisher":{"kind":"domain","id":"psychevus.com","label":"psychevus.com","url":"https://psychevus.com"},"website":"https://psychevus.com/tools","repository":"","remotes":[{"type":"streamable-http","url":"https://psychevus.com/api/mcp"}],"packages":[],"published":"2026-11-18","updated":"2026-11-18","status":"online","auth":"","latency_ms":998,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"check_email_domain","title":"Inbox check","description":"Assess, from public DNS, whether a domain's email is set up to be trusted by inboxes and to resist impersonation. It can't see a provider's spam filtering or the domain's sending reputation. Reads the domain's public SPF, DKIM and DMARC records and returns plain-language answers (can its mail prove where it comes from, as Gmail and Outlook require; does its policy ask inboxes to block forgeries of","read_only":true},{"name":"find_lookalike_domains","title":"Lookalike domain radar","description":"Look for registered lookalikes of a domain that could be used to impersonate it (other endings, look-alike characters like rn for m, an added word such as -billing, typos). Generates about 70 candidates, reads public DNS and registry (RDAP) data for them, and reports which exist, which can receive email, which were registered recently, and which are probably the owner's own. A lookalike outside th","read_only":true},{"name":"analyze_email_headers","title":"Email header analyzer","description":"Read what the mail servers recorded about one received email, to help explain why it was trusted, filed as spam or looks fraudulent: SPF, DKIM and DMARC results with alignment, Microsoft SCL and SpamAssassin verdicts, a Reply-To pointing at another domain, each delivery hop with delay and encryption, and one-click unsubscribe. Pass the full header block as the user copied it (Gmail: Show original)","read_only":true},{"name":"verify_email_signature","title":"Email signature check (DKIM)","description":"Verify the DKIM signatures of one raw email (headers and body, as copied from Gmail's Show original or a .eml file): recomputes the body hash, canonicalises the signed headers and checks each signature against the key the signing domain publishes in DNS (RFC 6376, 8301, 8463). Reports, as separate results: whether each signature is cryptographically valid; which domain signed; whether it is curren","read_only":true},{"name":"count_spf_lookups","title":"SPF lookup counter","description":"Count the DNS lookups an SPF record would cost with the given include hostnames, nested includes resolved live, against the RFC 7208 limit of 10. Use it before proposing a merged SPF record.","read_only":true},{"name":"check_payment_change_request","title":"Payment-change check","description":"Weigh an email asking to change a supplier's (vendor's) bank details, one of the costliest forms of business email compromise. Compares the sender (and Reply-To) with the supplier's real domain for lookalike tricks (other endings, look-alike or other-alphabet characters, typos, added words, the supplier's name in front of another domain), reads the sender domain's registration age and the supplier","read_only":true},{"name":"check_payment_policy","title":"Payment policy (payment-policy.txt)","description":"Read a business's payment-policy.txt (https://<domain>/.well-known/payment-policy.txt): how it changes bank details (for example never by email), which domains its invoices come from, and fingerprints of the accounts it is paid into. Pass an account to check whether it is on the business's published list (compared here, never stored); a match can't rule out that whoever controls the website change","read_only":true},{"name":"assess_callback_record","title":"Bank-change callback check","description":"Check the facts of a callback that verified a supplier's bank-detail change against the rules auditors and social-engineering insurance usually require: the number called came from a source that predates the request, never from the request itself (pass requestText and every phone number in it is compared); the call followed the request; the person reached confirmed the holder and read out the same","read_only":true},{"name":"verify_callback_record","title":"Verify a saved callback record","description":"Verify a callback record file saved by https://psychevus.com/tools/payment-check/callback-record. It answers three questions separately (layers): integrity (both digests, the sealed verdict, the approval refers to this exact record), history (both timestamps against this site's published keys; the call dated no more than 3 days before the record was sealed and not after it; the request not dated a","read_only":true},{"name":"timestamp_digest","title":"Timestamp a SHA-256 digest","description":"Get a signed timestamp (compact JWS, EdDSA, verifiable with https://psychevus.com/.well-known/psychevus-proof-keys.json) stating that psychevus.com saw this SHA-256 digest at this second. Use it to make an audit record (a callback record, an approval) tamper-evident: hash the canonical record yourself and pass only the 64 hex characters; the content is never sent. Pass token instead to verify an e","read_only":true},{"name":"check_dns_propagation","title":"DNS propagation watch","description":"After a DNS change, check whether four public resolvers (Cloudflare, Google, NextDNS, AdGuard) already return the new SPF, DMARC, DKIM, MTA-STS, TLS-RPT or BIMI record, and how long caches may keep the old one. Pass the value just published as expect to compare.","read_only":true},{"name":"analyze_supabase_rls","title":"Supabase RLS attack simulator","description":"Given a Supabase schema (supabase db dump output, migrations, or CREATE TABLE / ALTER TABLE ... ENABLE ROW LEVEL SECURITY / CREATE POLICY / CREATE VIEW / CREATE FUNCTION statements), work out for every table exposed through the Data API and every command whether anyone with the public anon key, any signed-in user, only the row's owner, or nobody can do it, applying PostgreSQL's policy rules. Flags","read_only":true},{"name":"check_app_exposure","title":"Web app exposure check","description":"Passive check of a public web app (for example one built with Lovable, Bolt, v0, Cursor or Claude Code): downloads its page and the same-site scripts that page loads, exactly as a browser would, and reports secret keys in the public JavaScript (Supabase service_role, Stripe secret, OpenAI, Anthropic and others, redacted), public source maps, client-side Supabase/Firebase exposure and missing secur","read_only":true},{"name":"check_email_sender","title":"Is this email really from them?","description":"Given a company's domain and the sender address of an email that claims to be from it, say whether the address is on the company's own domain or a subdomain of it, a lookalike made to pass as it (look-alike characters, another ending, a typo, an extra word, or the name in front of someone else's domain), a free mail account or an unrelated domain. For the company's own domain, also reads the DMARC","read_only":true}],"server_info":{"name":"psychevus-inbox-check","title":"Psychevus security tools","version":"2.6.0"},"category":"communication","tags":["security","finance","data"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-11","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/com-psychevus-email-security/"}