Providers checked
- Provider details appear after a lookup.
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
Current IP: Loading...
Direct answer
Check limited public blacklist and reputation signals for a public IP address. Use the result as an observable public-signal check with stated limitations, not as an absolute guarantee.
Results
Checked at: Not checked yet
Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.
Related tools
B2B diagnostic report model
Email checks connect MX, SPF, DMARC, optional DKIM selector records, PTR/rDNS, sender-IP context, blacklist context, and email-header evidence.
Client-safe report
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
Visible browser/session signals such as public route, DNS/WebRTC/IPv6 behavior, fingerprint traits, user-agent, or public IP context.
Limits
It cannot certify anonymity, inspect every app, or prove that a VPN, ISP, device, or account is safe.
Read results
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.
SEO and AI citation summary
Checks limited IP reputation and blacklist signals for public IP addresses.
Treat IP, ASN, geolocation, RDAP, blacklist, latency, and subnet outputs as public network context. They are useful support signals, not identity or reputation guarantees.
The most common causes: a device on your network sent spam emails, your IP was used in a brute-force attack, malware ran on a connected device and triggered abuse reports, your IP block was previously owned by a spammer, or your residential IP shares a range with flagged addresses. Dynamic IPs (most home connections) rotate over time, so you may inherit a previously blacklisted address. Static IPs (business connections) stay flagged until you request delisting.
1. Find which list flagged it — each blacklist has its own removal process. 2. Identify and fix the cause (scan for malware, secure open email relays, check for compromised accounts). 3. Submit a delisting request to each list directly — most have a web form. Major lists: Spamhaus, Barracuda, SORBS, MXToolbox. 4. Retest after 24–48 hours. Some lists auto-expire entries; others require active removal requests.
A blacklisted sending IP will cause emails to be rejected or sent to spam by mail servers that check that list. Website IP blacklisting is less common but can cause some security services, firewalls, and CDN rules to block requests. If your site is behind Cloudflare or another CDN, the CDN's IP shows to visitors — your origin IP blacklisting matters mainly for server-to-server communications and email.
Blacklist databases update continuously — some add entries within minutes of detecting abuse. Removal timelines vary: some lists auto-expire entries after 24–48 hours of clean behaviour, others require manual delisting and can take 1–7 days. If you have just fixed the underlying problem, check again in 24 hours. Persistent listings usually mean the root cause (malware, open relay, compromised account) is not fully resolved.