IP abuse report74.82.47.3
74.82.47.3 is an IPv4 address located in Pleasanton, 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 Hurricane Electric LLC · 2026-09-22 · IPDB-AR-000022 Awaiting reply Show detailsHide
- DetectedScore 100/100
- Notice sent2026-09-22 23:25
- Deliveredhe.net
- Operator response Waiting · 1 month ago
The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Hurricane Electric LLC's registered abuse contact on 2026-09-22 23:25: abuse@he.net
IP Information
- ISP / Organization
- Hurricane Electric LLC
- ASN
- AS6939 HURRICANE
- ASN Domain
- he.net
- IP Range
- 74.82.0.0/18
- Regional Registry
- ARIN
- Connection Type
- Hosting / Datacenter
- Country
- United States (US)
- Region / State
- California
- City
- Pleasanton
- Time Zone
- Unknown
- 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.70, -121.90
- 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
74.82.47.0/2461 of the 256 addresses in 74.82.47.0/24 are listed by our sources (23.8%).
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-08 05:17 | 2026-11-20 03:182 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| CZ.NIC Turris Sentinel Greylist | Single address | 2026-11-17 02:17 | 2026-11-20 03:173 minutes ago |
| IP-DB Sensor Network | Single address | 2026-10-30 17:18 | 2026-11-20 03:20just now |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Malicious IP (romainmarcoux) Aggregator | Single address | 2026-11-07 19:33 | 2026-11-20 03:192 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 74.82.47.3 login attempt root / ••••••
- 14:02:10 globalprotect:443 74.82.47.3 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 74.82.47.3 password spray Exchange OWA
- 14:02:16 netscaler:8443 74.82.47.3 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=FTP; application_protocol=FTP; transport=TCP; destination_port=21; observed_at=2026-11-13T12:51:18Z; last_observed_at=2026-11-13T12:51:18Z; reported_at=2026-11-13T12:51:19Z matched_log_events=2; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=21 2026-11-13T12:51:18Z FTP/21 activity=client data bytes=10 commands=AUTH arguments=<redacted> 2026-11-13T12:51:18Z FTP/21 activity=connection accepted
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 74.82.47.3
Is 74.82.47.3 safe?
No. 74.82.47.3 scores 100/100 with strong, recent evidence of abuse (4 sources, 1 community report). Blocking it at your firewall is advisable.
Who owns 74.82.47.3?
74.82.47.3 is announced by AS6939 and operated by Hurricane Electric LLC. It sits in the 74.82.0.0/18 block registered with ARIN.
Where is 74.82.47.3 located?
Geolocation places 74.82.47.3 in Pleasanton, United States. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 74.82.47.3 on a blacklist?
Yes. 74.82.47.3 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 74.82.47.3?
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/74.82.47.3