Mail servers
Look for MX records showing whether the domain is configured to receive email.
Display names are easy to imitate, and a familiar-looking address can use a subtly different domain. Domain-level signals help explain whether a sender address has normal mail infrastructure and whether the domain is unusually new or resembles a known brand.
SPF and DMARC are useful authentication signals, but their presence does not prove that a specific message or sender is legitimate. Treat them as part of the evidence, not a green light.
Look for MX records showing whether the domain is configured to receive email.
Report published sender-authentication policies and important policy context.
Use RDAP registration data when available as a contextual signal.
Check for domain spellings that may imitate a recognizable brand.
This documented regression fixture shows the same classifications used by the Universal Safety Checker.
The reserved .example address exercises the lookalike detector without checking a real person's mailbox.
No scanner can guarantee that a link, sender or website is safe. A result can report known threats and warning signals, but it cannot prove identity, business legitimacy, licensing, product quality or future behavior. For sensitive actions, verify the organization independently.
No. They help authenticate permitted sending infrastructure and domain policy, but a legitimate domain can still send an unwanted message or have a compromised account.
It is a reason for extra verification, not proof of fraud. Many legitimate organizations also use recently registered domains.
Not reliably without interacting with the mail provider, which can be inaccurate and privacy-invasive. The checker focuses on domain-level signals.
No. The email path uses email and domain checks rather than sending the email address to the URL threat-list service.
Paste the suspicious link or email address into the same checker. You will get the destination, available threat signals and a plain-language recommendation without a signup.
Check a link or emailLast reviewed: 2026-09-03 · Can I Share This? safety content
Checks whether the submitted address has a supported, plausible email structure.
Looks for DNS evidence that the domain exists and can receive or publish email-related records.
Checks whether the domain publishes mail-exchanger records when DNS data is available.
Inspects published sender-authentication policy signals. Missing or weak policy is context, not proof of fraud.
Flags domains that visually resemble selected well-known brands but are not recognized official domains.
Identifies a maintained set of known temporary-email providers as a contextual warning signal.
Uses public RDAP registration data when available. A new domain can deserve more scrutiny but is not automatically malicious.
Highlights punycode or internationalized-domain encodings that can sometimes make visual impersonation harder to notice.
It cannot prove who controls a mailbox, guarantee that a sender is legitimate, or authenticate the exact message from an address alone. Display-name spoofing and message-level social engineering require the full message context.
For a suspicious email, verify the company through a website or app you already trust rather than using the contact details or links inside the message.
Phishing reference: U.S. Federal Trade Commission — How to recognize and avoid phishing scams.