A simple reference for the records that control email routing, authentication and policy.
Authorize.email reads publicly available DNS information for a domain and presents the email configuration in a clear, human-readable format.
MX records tell other mail systems where email addressed to your domain should be delivered.
If a domain has no MX records, receiving mail may not be configured for that domain.
Sender Policy Framework identifies the mail servers and services authorised to send email using a domain.
SPF policies are published as TXT records at the domain level.
DomainKeys Identified Mail allows receiving systems to verify a cryptographic signature attached to outgoing messages.
The selector is chosen by the sending system. Different providers may therefore use different selectors.
DMARC tells receiving systems how a domain wants messages handled when SPF and DKIM authentication does not align with the visible From domain.
See the live DNS configuration in seconds.
Sovereign Seal adds a verifiable identity layer to email. While SPF, DKIM and DMARC establish sending authorisation, cryptographic authentication and domain policy, Sovereign Seal is designed to associate a domain with a recognisable sender identity.
A Sovereign Seal can identify the organisation or company operating a domain and provide structured identity information that participating systems can use when presenting or verifying a sender.
Sovereign Seal information is published through DNS using a dedicated _seal record. This allows the identity layer to remain separate from traditional email authentication records while remaining publicly discoverable.
The company or organisation information associated with a Sovereign Seal provides context about who stands behind the domain. This is different from simply proving that a server was authorised to send mail.
For example, a domain may authenticate its mail correctly through SPF, DKIM and DMARC while still providing little visible information about the organisation operating the domain. Sovereign Seal is intended to bridge that identity gap.
A participating mail client, service or verification system can retrieve the published Sovereign Seal information, validate the cryptographic material and associate the verified domain with its published sender identity.
Email authentication answers questions such as whether a sending system was authorised and whether a message's cryptographic signature can be verified. Identity answers a different question: who is behind the domain?
Sovereign Seal is designed to make that identity machine-readable and discoverable, allowing participating software and mail clients to move beyond a raw domain name and understand the organisation associated with it.
Authorize.email is being built as a programmable email intelligence layer for AI agents that need to understand, verify and interact with email infrastructure.
An agent can inspect a domain, understand its authentication configuration, verify sender identity and make informed decisions about email infrastructure before taking action.
Authorize.email turns otherwise complicated DNS and email infrastructure into understandable signals that software and AI agents can consume. The agent does not need to manually interpret raw DNS records before deciding what to do next.
Authorize.email provides the intelligence layer. Sovereign Seal provides the sender identity and company context layer. Firetip provides the outbound delivery infrastructure. Together they create an email stack that an AI agent can actually use.
Get direct architectural guidance on email delivery, authentication, DNS, SMTP infrastructure and sovereign communications.
Book a Consultation ↗