MyIPScan
Selected sources

IP Blacklist Checker

Check a public IPv4 address against selected blacklist and reputation sources with source-by-source results.

MyIPScan only reports what the configured sources return. A "not listed" result means not listed on the checked sources, not a guarantee that an IP is safe.

Lookup

Check an IP

Ready

Current IP: Loading...

Results

Blacklist check

Enter a public IPv4 address to check selected blacklist sources.

Checked at: Not checked yet

Providers checked

  • Provider details appear after a lookup.

Limitations

  • Only selected sources are checked.
  • Not listed does not guarantee an IP is safe.
  • Listed does not always prove malicious activity.
  • Blacklist and reputation databases can be stale or incomplete.
  • IPv6 support depends on provider coverage.
Want the full picture? Run the Privacy Exposure Report.

Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.

Run report Scan website Check email exposure

Related tools

Continue the privacy check

B2B diagnostic report model

Email domain diagnostics

Email checks connect MX, SPF, DMARC, optional DKIM selector records, PTR/rDNS, sender-IP context, blacklist context, and email-header evidence.

SummaryStart with a plain-language status for the public target.
Top issuesPrioritize the few findings that need attention first.
What passedShow expected public signals without turning them into a certification.
What needs reviewSeparate limited, unavailable, and review-worthy signals.
Why it mattersExplain the business, delivery, crawl, or implementation impact.
Recommended fixesPoint to the DNS, hosting, email, CMS, or SEO owner who can act.
What this tool cannot checkThis does not send mail, inspect private mailboxes, guarantee inbox placement, or certify sender reputation everywhere.
Client-safe copyClient-safe copy should keep authentication findings and fixes while removing email local-parts, raw TXT payloads, raw sender IP details, and private mailbox context.
Monitoring beta (optional)Optional monitoring beta can compare MX, SPF, DKIM selector checks, DMARC policy, PTR/rDNS, and selected blacklist signals for approved domains.

Client-safe report

Share findings without leaking raw technical material

Use Safe Copy or this page's summary when sending results to a client, vendor, developer, or support team. Raw headers, credentials, tokens, cookies, private addresses, email local-parts, and oversized payloads should stay out of client-facing copy.

Check my browser/privacy

What this checks

Visible browser/session signals such as public route, DNS/WebRTC/IPv6 behavior, fingerprint traits, user-agent, or public IP context.

Limits

What this cannot check

It cannot certify anonymity, inspect every app, or prove that a VPN, ISP, device, or account is safe.

Read results

How to use the output

Treat results as review signals for this browser/session or public target. Re-test after one change, then use Safe Copy or notes that avoid raw identifiers.