F
InboxDoctor · Deliverability report

neverssl.com

Scanned Jul 12, 2026, 12:40 PM · public DNS only, no mail sent
Score 8/100 — grade F

This report checks whether neverssl.com is set up so its email reaches the inbox instead of spam. It inspects the domain's SPF, DKIM, DMARC and MX records over public DNS — no mail is sent. neverssl.com currently scores 8/100 (grade F).

Check your own domainFree, instant, no signup — public DNS only.

Prioritised fixes

  1. DMARC
    Publish a TXT record at _dmarc.neverssl.com to start in monitoring mode:
      v=DMARC1; p=none; rua=mailto:dmarc@neverssl.com
  2. SPF
    Publish a TXT record at the root of neverssl.com:
      v=spf1 include:_spf.your-provider.com ~all
  3. DKIM
    Enable DKIM signing in your mail platform and publish the key it gives you. If you already use a custom selector, re-run with --selectors <name> to confirm.
  4. MX Records
    Add an MX record pointing to your mail provider, e.g.
      neverssl.com.  IN MX 10 mx.your-provider.com.

Full results for neverssl.com

✕ FAIL

MX Records

0/15

No MX records found. This domain cannot receive email, and many providers treat a missing MX as a strong spam signal.

How to fix
Add an MX record pointing to your mail provider, e.g.
  neverssl.com.  IN MX 10 mx.your-provider.com.
✕ FAIL

SPF

0/25

No SPF record found. Receivers cannot verify which servers are allowed to send as your domain — a top reason mail is marked as spam or spoofed.

How to fix
Publish a TXT record at the root of neverssl.com:
  v=spf1 include:_spf.your-provider.com ~all
✕ FAIL

DMARC

0/30

No DMARC record found. Without DMARC, receivers have no instruction on what to do with mail that fails SPF/DKIM, and you get zero visibility into who is spoofing you. From 2024, Google and Yahoo require DMARC for bulk senders.

How to fix
Publish a TXT record at _dmarc.neverssl.com to start in monitoring mode:
  v=DMARC1; p=none; rua=mailto:dmarc@neverssl.com
! WARN

DKIM

8/25

No DKIM key found on any common selector. Your mail may still be signed with a custom selector we could not guess — but if it is not, receivers cannot cryptographically verify your messages.

How to fix
Enable DKIM signing in your mail platform and publish the key it gives you. If you already use a custom selector, re-run with --selectors <name> to confirm.
i INFO

Advanced (MTA-STS · TLS-RPT · BIMI)

0/5

No MTA-STS, TLS-RPT or BIMI found. These are optional but boost security and, for BIMI, show your logo in the inbox.

How to fix
Consider MTA-STS (enforce TLS), TLS-RPT (TLS failure reports), and BIMI (brand logo in Gmail/Apple Mail) once SPF/DKIM/DMARC are solid.