IP abuse report184.105.247.252
184.105.247.252 is an IPv4 address located in San Francisco (South Beach), United States. It belongs to a network operated by Hurricane Electric LLC (AS6939). The address is listed by 4 of the threat-intelligence sources we track and carries a confidence score of 100/100. It has also been reported 1 time(s) by the community.
Provider notified This IP was reported to its network operator The Shadowserver Foundation, Inc. · 2026-11-10 · IPDB-AR-007187 Awaiting reply Show detailsHide
- DetectedScore 100/100
- Notice sent2026-11-10 12:33
- Deliveredshadowserver.org
- Operator response Waiting · 9 days ago
The IP-DB Abuse Desk sent an abuse notice with supporting evidence to The Shadowserver Foundation, Inc.'s registered abuse contact on 2026-11-10 12:33: abuse@shadowserver.org
IP Information
- ISP / Organization
- Hurricane Electric LLC
- ASN
- AS6939 HURRICANE
- ASN Domain
- he.net
- IP Range
- 184.104.0.0/15
- Regional Registry
- ARIN
- Connection Type
- Hosting / Datacenter
- Country
- United States (US)
- Region / State
- California
- City
-
San Francisco (South Beach)Local databaseShawneeLive service
The two sources report different cities. Neither is confirmed; the country is the reliable part.
- Time Zone
- America/Chicago
- Abuse contact
- abuse@he.net The abuse mailbox this network lists with its regional registry. Report traffic from this IP here, with logs and timestamps.
City is an estimate. The country is reliable; the city varies by provider.
Approximate location
City level- Coordinates
- 37.78, -122.39
- Network
- AS6939 Hurricane Electric LLC
The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.
Network Neighbourhood
184.105.247.0/2446 of the 256 addresses in 184.105.247.0/24 are listed by our sources (18.0%).
Only a small part of the block is listed, which is more consistent with an isolated incident than with the network itself.
An address is not guiltier for having a few listed neighbours, which is why this stays out of the confidence score entirely while the block is mostly clean. It contributes at most 20 points, and only once a substantial share of the block is listed — that ceiling is deliberate: neighbours alone can raise an address to "low" and no further.
Threat Evidence
Last 30 days: how many feeds listed this address each day, and the community reports filed.
What this address is listed for: feed categories count sources, community categories count reports.
Where community reports were filed from. Only the reporter's country is shown, never their address.
Top reporter countries
- Canada1
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
4In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 02:50
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| IPsum (4+ lists) Aggregator | Single address | 2026-11-15 05:18 | 2026-11-20 03:183 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| CZ.NIC Turris Sentinel Greylist | Single address | 2026-11-20 02:17 | 2026-11-20 03:174 minutes ago |
| IP-DB Sensor Network | Single address | 2026-11-04 16:49 | 2026-11-20 03:201 minute ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Malicious IP (romainmarcoux) Aggregator | Single address | 2026-11-07 19:33 | 2026-11-20 03:193 minutes ago |
“Confirmed” is the moment the address was still on that source at its most recent fetch — the feeds are replaced wholesale on every refresh. Per-source “first seen” only began being recorded on 30 August 2026, so for listings older than that this column shows the start of record-keeping. The address-level history is the “in our pool since” value above.
Catch addresses like this on your own server
Sensor opens realistic decoy services — FortiGate, GlobalProtect, Exchange, NetScaler and more — on your server's unused ports. Every address that touches them is logged with evidence, and your firewall, fail2ban and Shield pull the same list to block it.
- Realistic decoys for VPN gateways, mail, web panels and databases
- Names exploit attempts by their CVE signature
- One-command install; runs unprivileged and never touches your real services
While a Sensor reports, your daily API quota rises to 30,000 lookups.
- 14:02:07 ssh:22 184.105.247.252 login attempt root / ••••••
- 14:02:10 globalprotect:443 184.105.247.252 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 184.105.247.252 password spray Exchange OWA
- 14:02:16 netscaler:8443 184.105.247.252 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 1
Report This IPWho reported this address, when, and on what grounds.
-
Alex Registered memberReason: Port Scan
Fail2Ban report from custom-honeypot; service=SMB; application_protocol=SMB; transport=TCP; destination_port=445; observed_at=2026-11-11T14:05:27Z; reported_at=2026-11-11T14:05:28Z 2026-11-11T14:05:27Z activity=connection accepted 2026-11-11T14:05:27Z activity=negotiate data bytes=51 sha256=3f01fe01fd2e2397
Reporters' IP addresses are never published — only the country they reported from.
Listing History
1The pool is a live picture: an address listed today leaves it when the sources drop it. This record outlives that removal — “listed on 12 August, delisted on 3 September” is truer than either a permanent accusation or a blank page. Events are kept for 400 days.
Frequently asked questions about 184.105.247.252
Is 184.105.247.252 safe?
No. 184.105.247.252 scores 100/100 with strong, recent evidence of abuse (4 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 184.105.247.252?
184.105.247.252 is announced by AS6939 and operated by Hurricane Electric LLC. It sits in the 184.104.0.0/15 block registered with ARIN.
Where is 184.105.247.252 located?
Geolocation places 184.105.247.252 in San Francisco (South Beach), United States. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 184.105.247.252 on a blacklist?
Yes. 184.105.247.252 is currently listed by 4 threat sources: CZ.NIC Turris Sentinel Greylist, IPsum (4+ lists), Malicious IP (romainmarcoux), IP-DB Sensor Network.
How do I report abuse from 184.105.247.252?
Send your log lines to the network's abuse contact, abuse@he.net, and file a report on IP-DB so others can see it too.
Run this check via the API
The same score and evidence are available as JSON, free with an API key.
API documentation →curl -H "Key: YOUR_API_KEY" https://ip-db.com/api/v1/check/184.105.247.252