See how a domain handles email.

Use the profile to add a mail provider to a CRM record, compare the networks used by a domain’s mail servers and website, or check when a new customer’s domain was registered. Choose Standard for mail configuration and networks. Extended includes everything in Standard and adds registration details.

The lookup opens no SMTP session and sends no email. It cannot confirm that a particular mailbox exists, that its owner wants your email or that a message will reach the inbox.

Find the incoming mail route and provider

Mail routing shows whether the domain has somewhere to receive mail. MX records name the receiving mail servers and their priorities; a lower number means a server is preferred. A domain without MX records may still route mail through its own IP addresses. The profile can also show that the domain does not exist, declares that it accepts no mail, or has a configuration problem.

When the preferred MX servers all match the same known operator, the profile names that provider. Different operators produce a mixed match; an unrecognised server leaves the match unknown. The identified operator may be a filtering gateway that passes mail to another provider, so it may not be the company hosting the mailboxes.

Interpret provider classifications and catch-all behaviour

Reference data identifies known disposable-mail providers, which offer temporary addresses, and public providers, which offer consumer mailboxes. A domain absent from these lists has not been established as safe or corporate.

A catch-all mail server accepts recipients broadly enough that acceptance cannot confirm a particular mailbox exists. The profile reports any catch-all state Emvero already holds for the domain. This lookup does not test a new recipient, so the state may remain unknown.

Read the published SPF and DMARC records

SPF describes which servers are authorised to send using a domain. DMARC publishes a policy for handling messages that fail authentication checks against the domain in the visible From address. These records concern outgoing mail; they do not establish whether the domain can receive it.

Domain Intelligence reads the records, checks their syntax and reports the supported settings. It does not authenticate a message or follow the policies referenced by SPF includes to test a sender. The guide to SPF and DMARC explains these checks and how they differ from MX routing.

Compare the networks used by mail and the website

Both modes show public IP addresses for the mail servers and the domain you entered. The profile also lists any DNS aliases followed to resolve that domain, called the CNAME chain. Each address can have an autonomous system number (ASN), identifying the network that announces its route on the internet. Available network details include a name, registration country and type, such as hosting or an internet provider.

These details let you compare the infrastructure behind mail and the website. If a recognised content delivery network (CDN) or proxy is visible, the profile names it; its addresses may conceal the origin server. The network’s registration country does not establish the server’s location, and resolving an IP address does not test whether the website responds.

Check registration details with Extended

Extended reads registration details from the domain registry through RDAP, a protocol for accessing registry records. When available, the profile includes the registration date, age in days, expiry date, registrar and registry statuses. For a subdomain, these details describe the registered parent domain.

The date tells you how old the registration is. It does not establish the age of the company or website, or when the current owner acquired the domain. Some registries do not support RDAP or omit the date; the profile explains why it is unavailable. Registration age and network details alone do not establish that a domain is trustworthy.

Check completeness and the age of each observation

Each part of the profile shows its source, status and available observation dates. Unknown means the evidence could not settle that field. Stale data describes an earlier observation whose refresh failed. Check these details for the fields you need before relying on them.

A complete profile means the required observations for the selected mode were processed without errors or stale data. The provider or catch-all state can still be unknown, and the routing result can show that the domain accepts no mail. Network data has its own status and does not determine the profile’s completeness or price.

An Extended profile is partial when the registration date is missing. Incomplete Standard observations also make the profile partial. If the source needed to establish routing fails, the service returns an error; that does not mean the domain has no mail route.

In this example, incoming mail has an MX route, but no single mail provider has been identified. Mail and website addresses share network AS64500; one mail server address belongs to AS64511. The registration is 2,191 days old when the profile is generated. SPF publishes -all and DMARC publishes reject: neither is a result from testing a message. The catch-all state remains unknown even though the profile is complete.

For a fuller walkthrough, see how to read a domain intelligence profile.

Run a lookup from your account

Create an account or sign in, then open Domain Intelligence. Enter a domain on its own, such as example.com, with no email address, URL or wildcard, and choose Standard or Extended. A subdomain is checked as entered; its mail route may differ from the parent domain’s.

Both modes use the shared account balance. Returning a saved answer on retry adds no charge; the original lookup’s cost still applies. If a charge cannot be confirmed, credits may already have been deducted. Use the retry option in your account to check the same operation.

To look up domains from your own server, use the Domain Intelligence API. It returns the same profile and documents safe retries and billing fields.