IP abuse report65.49.20.68

Critical Hosting / Datacenter IPv4 United States AS6939

65.49.20.68 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 6 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.

Last updated Listing sources 6 Community Reports 1 How the score works
Provider notified This IP was reported to its network operator Hurricane Electric LLC · 2026-11-17 · IPDB-AR-007935 Awaiting reply Show detailsHide
  1. DetectedScore 100/100
  2. Notice sent2026-11-17 13:34
  3. Deliveredshadowserver.org
  4. Operator response Waiting · 2 days ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to Hurricane Electric LLC's registered abuse contact on 2026-11-17 13:34: abuse@shadowserver.org

This notice covers 12 address(es) on the same network. View public record · IPDB-AR-007935 →
Listing sources6
Community Reports1
Distinct Reporters1
Last seen 31 minutes ago

IP Information

ISP / Organization
Hurricane Electric LLC
ASN
AS6939 HURRICANE
ASN Domain
he.net
IP Range
65.49.20.64/26
Regional Registry
ARIN
Connection Type
Hosting / Datacenter
Country
United States (US)
Region / State
California
City
Pleasanton 2 sources agree
Time Zone
America/Los_Angeles
Abuse contact
abuse@shadowserver.org 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
Pleasanton California, United States
Coordinates
37.70, -121.90
Network
AS6939 Hurricane Electric LLC
Open on the threat map

The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.

Network Neighbourhood

65.49.20.0/24

61 of the 256 addresses in 65.49.20.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.

Examples from the same block
65.49.20.6665.49.20.6765.49.20.6965.49.20.7065.49.20.7165.49.20.7265.49.20.7365.49.20.74

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.

Blocklist feeds Community reports

Blacklist Matches

6

In our pool since: 2026-08-28 11:17 (2 months ago) · Last confirmed: 2026-11-20 02:50

Aggregated List (High Confidence) 1
SourceScopeFirst seenConfirmed
IPsum (4+ lists) Aggregator Single address 2026-11-09 05:18 2026-11-20 03:182 minutes ago
Aggregated List (Low Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 3 Aggregator 65.49.20.0/24 2026-11-07 19:33 2026-11-20 03:182 minutes ago
Attack Source 2
SourceScopeFirst seenConfirmed
CZ.NIC Turris Sentinel Greylist Single address 2026-11-20 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
Malicious Activity 2
SourceScopeFirst seenConfirmed
CINS Army List Single address 2026-11-20 03:17 2026-11-20 03:174 minutes ago
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.

IP-DB Sensor · free honeypot

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.

root@web-01 — ipdb-sensor DEMO
● ipdb-sensor.serviceactive (running)
4hits
4decoys
1blocked
  1. 14:02:07 ssh:22 65.49.20.68 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 65.49.20.68 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 65.49.20.68 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 65.49.20.68 Citrix Bleed scan CVE-2023-4966
  5. 14:02:20 ✓ evidence logged → added to your blocklist
Sample output — if this address probed your server

Community Reports 1

Report This IP

Who reported this address, when, and on what grounds.

0Last 24 Hours
1Last 7 Days
1Last 30 Days
1Last 90 Days
  1. Alex Registered member
    3 days ago 2026-11-16 15:18Reported from: Canada (CA)
    Reason: Port Scan
    Fail2Ban report from custom-honeypot; service=Telnet; application_protocol=Telnet; transport=TCP; destination_port=23; observed_at=2026-11-16T12:18:16Z; last_observed_at=2026-11-16T12:18:16Z; reported_at=2026-11-16T12:18:17Z matched_log_events=2; evidence_window_seconds=30; logged_tcp_connections=1; destination_ports_seen=23 2026-11-16T12:18:16Z Telnet/23 activity=client data bytes=216 credentials=<redacted> 2026-11-16T12:18:16Z Telnet/23 activity=connection accepted

Reporters' IP addresses are never published — only the country they reported from.

Listing History

1
Added to the pool
2 months ago · score at the time: 90/100 · carried by 6 sources
2026-08-28 11:17

The 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 65.49.20.68

Is 65.49.20.68 safe?

No. 65.49.20.68 scores 100/100 with strong, recent evidence of abuse (6 sources, 1 community report). Blocking it at your firewall is advisable.

Who owns 65.49.20.68?

65.49.20.68 is announced by AS6939 and operated by Hurricane Electric LLC. It sits in the 65.49.20.64/26 block registered with ARIN.

Where is 65.49.20.68 located?

Geolocation places 65.49.20.68 in Pleasanton, United States. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 65.49.20.68 on a blacklist?

Yes. 65.49.20.68 is currently listed by 6 threat sources: CINS Army List, CZ.NIC Turris Sentinel Greylist, IPsum (4+ lists), Malicious IP (romainmarcoux), IP-DB Sensor Network, FireHOL Level 3.

How do I report abuse from 65.49.20.68?

Send your log lines to the network's abuse contact, abuse@shadowserver.org, 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/65.49.20.68

Guides for this IP