Blacklist Check: Domain, IP & Mailserver Check
DNSBL/RHSBL and mail DNS verification. No Google Safe browsing test and no statement about rankings. MX-IP and actual shipping IP can be different.
Give them a Domain, IP or URL and then check them out. DNSBL/RHSBL blacklists, MX-IP(s), hits and reputation hints.
- A hit does not automatically mean “spam” – check which list and whether it is MX-IP Or website IP.
- With CDN or shared hosting, a website IP can be used by several customers. Clarify the relation to your own service.
- For hits: Check reputation, SPF/DKIM/DMARC, bounce rates and abuse.
- Input normalization: URL → Host, Domain → Host
- DNS: A/AAAA IPs + MX hosts → IPs
- IP checks: DNSBL queries per IP (multiple zones)
- Domain Check: RHSBL/SURBL (Simplified Domain Check)
- Result: Hits, Details, Score & Notes
A small piece of Seitenreport is yours.
Show your company, your product or your idea. Choose your place and present your website in the gallery of this tool.
Free seats are loaded ...
| IP | List | Status | Details |
|---|---|---|---|
| No data yet. | |||
| Domain | List | Status | Details |
|---|---|---|---|
| No data yet. | |||
Correctly classify a listed MX-IP
Practical example · for illustration
Starting position
Example: The domain receives emails via an MX host; its IP appears in a DNSBL.
Classify the findings
This occupies a listing of the requested IP in this list. The MX host denotes the incoming mail path and does not have to be the outgoing shipping server.
Specific amendment
In the case of delivery problems, determine the actual sending IP from mail headers, bounce messages or provider details and check them separately.
Control and border
First clarify cause and shipping reference, then check with the list operator according to its procedure or delist. A DNSBL hit is not a Google Safe browsing or ranking finding.
What DNSBL and RHSBL hits say
The check queries configured DNS-based lists for IP addresses and domains and complements the mail DNS context. A hit applies to the respective destination, the respective list and the query time. Not every recipient page uses the same lists. Provider or resolver warnings are not confirmed listings.
MX is the incoming mail route
MX records name servers that receive emails for a domain. Outbound shipping can run through other IPs or an external shipping service. In case of delivery problems, determine the actual sending IP from a bounce message, the received headers of a delivered message or the mail provider and check it specifically.
No safe browsing or ranking test
DNSBL/RHSBL lists are not Google Safe Browsing. This tool does not check Google’s security alerts, manual actions or rankings. A hit on a shared hosting IP is therefore not proof that your website is dangerous or ranks worse on Google.
Resolve hits and re-check
List operators and affected IP or domain confirm, clarify causes such as compromised shipping or shared hosting problems and then consider the respective delisting procedure. SPF, DKIM and DMARC must match the actual shipment; the mere presence of DNS records does not guarantee delivery.
Questions about use and boundaries
Is a listed MX-IP my shipping IP?
Not mandatory. MX refers to the incoming mail route. The actual sending IP must be determined on the basis of mail headers, bounce messages or provider information.
Does the tool Google Safe Browsing check?
No. DNSBL and RHSBL lists as well as mail DNS are checked. This does not lead to any statement about Google security warnings or rankings.
Does no hit mean that every email is delivered?
No. Only the configured, successfully queried lists were checked. Recipient filters, shipping behavior and authentication can additionally influence delivery.