MXMXBLACKLISTmxblacklist.info

THE MAIL DNS + SENDING-IP DESK

Understand What’s
Behind the Bounce.

Inspect mail records or check a sending IP. Read the evidence, know the limits, and choose the next useful step.

01

START WITH THE RIGHT TARGET

Choose Your Check

Diagnostic mode

Use a public domain, not an email address or URL. This checks records at the exact name you enter.

Mail DNS uses 3 lookup units. Your shared lookup allowance is 6 units per minute.

Lookup only. We never submit spam reports or removal requests. Need help with a listing?

Which IP Should I Check?

Use the public sending-server IP from a bounce or trusted mail log. Your web connection IP and a domain’s incoming MX servers may be completely different from the system that sent the message.

IPv4 gets a SpamCop check and PTR lookup. IPv6 gets PTR only; its blocklist state remains explicitly “not checked.”

02

EVIDENCE BEFORE ASSUMPTIONS

Your Diagnostic Snapshot

Ready When You Are.

Enter a domain or sending IP and run a lookup. Results are fetched on request—no invented score or prefilled clean verdict.

  • Mail DNS: published MX, SPF and exact-name DMARC.
  • Sending IP: one blocklist with access checks, plus reverse DNS.
  • Clear limits: no SMTP probing, message sending or inbox-placement guarantee.
60 Requests / Minute / IPPages, assets and endpoints share this rolling HTTP allowance.
6 Lookup Units / Minute / IPMail DNS: 3 · IPv4: 4 · IPv6 PTR: 1. Failed checks still use the reserved units.
CLI / API Guide →

WHAT THE RESULT MEANS

One Check Is Not the Whole Story.

Receiving mail ≠ sending mail.

An MX record tells senders where to deliver incoming mail. It does not list every outbound service used by that domain.

Not listed ≠ guaranteed delivery.

Receivers also assess authentication, content, volume and their own policies. This site queries SpamCop only; it does not claim universal blocklist coverage.

Record found ≠ authentication passed.

SPF and DMARC publication is only one piece. A real message is needed to evaluate the relevant identities and alignment.

Follow the Delivery Checklist →

TERMINAL FRIENDLY

Your Public IP. One Command.

Just the source address seen by this web connection and one newline.

Terminal
curl mxblacklist.info

The bare command uses HTTP; use HTTPS for encryption. This returns your connection IP, not necessarily your mail server’s IP.

Copy Mail-DNS and PowerShell Examples →

READ THE SIGNAL. PICK THE NEXT STEP.

A Field Guide for Mail Troubleshooting.

01 / MAIL ROUTING

Read the Mail DNS.

MX preference, null MX, SPF and exact-name DMARC—with important boundaries.

5 min read02 / SENDING REPUTATION

Understand a Blocklist Result.

Listed, not listed and unknown mean different things. Know which IP to test and how to seek a review yourself.

7 min read03 / IN THE FIELD

Work Through a Bounce.

Follow a practical checklist before changing DNS or requesting delisting.

5 min read