IP abuse report180.178.61.134

Critical Residential IPv4 Japan AS963

180.178.61.134 is an IPv4 address located in Chiyoda City, Japan. It belongs to a network operated by N963 (AS963). The address is listed by 4 of the threat-intelligence sources we track and carries a confidence score of 90/100. No community reports have been filed for it yet.

Last updated Listing sources 4 Community Reports 0 How the score works
Provider notified This IP was reported to its network operator N963 · 2026-11-19 · IPDB-AR-008162 Awaiting reply Show detailsHide
  1. DetectedScore 90/100
  2. Notice sent2026-11-19 20:33
  3. Deliverednetsec.com
  4. Operator response Waiting · 7 hours ago

The IP-DB Abuse Desk sent an abuse notice with supporting evidence to N963's registered abuse contact on 2026-11-19 20:33: noc@netsec.com

This notice covers 1 address(es) on the same network. View public record · IPDB-AR-008162 →
Listing sources4
Community Reports0
Distinct Reporters0
Last seen 15 minutes ago

IP Information

ISP / Organization
N963
ASN
AS963 N963-AS-AP
ASN Domain
n963.com
IP Range
180.178.61.0/24
Regional Registry
APNIC
Connection Type
Residential
Country
Japan (JP)
Region / State
Tokyo
City
Chiyoda City
Time Zone
Unknown
Abuse contact
noc@netsec.com 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
Chiyoda City Tokyo, Japan
Coordinates
35.69, 139.75
Network
AS963 N963
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

180.178.61.0/24

No other address in 180.178.61.0/24 is listed.

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

Blacklist Matches

4

In our pool since: 2026-11-18 00:47 (2 days ago) · Last confirmed: 2026-11-20 03:49

Aggregated List (Medium Confidence) 1
SourceScopeFirst seenConfirmed
FireHOL Level 2 Aggregator Single address 2026-11-18 14:47 2026-11-20 03:4816 minutes ago
Attack Source 1
SourceScopeFirst seenConfirmed
Data-Shield IPv4 Blocklist Single address 2026-11-18 00:49 2026-11-20 03:4915 minutes ago
Malicious Activity 2
SourceScopeFirst seenConfirmed
ThreatView High Confidence Single address 2026-11-19 02:47 2026-11-20 03:4816 minutes ago
Malicious IP (romainmarcoux) Aggregator Single address 2026-11-19 09:48 2026-11-20 03:4916 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 180.178.61.134 login attempt root / ••••••
  2. 14:02:10 globalprotect:443 180.178.61.134 exploit attempt CVE-2024-3400
  3. 14:02:13 owa:4443 180.178.61.134 password spray Exchange OWA
  4. 14:02:16 netscaler:8443 180.178.61.134 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 0

Report This IP

No community reports yet for this IP.

Report This IP

Frequently asked questions about 180.178.61.134

Is 180.178.61.134 safe?

No. 180.178.61.134 scores 90/100 with strong, recent evidence of abuse (4 sources). Blocking it at your firewall is advisable.

Who owns 180.178.61.134?

180.178.61.134 is announced by AS963 and operated by N963. It sits in the 180.178.61.0/24 block registered with APNIC.

Where is 180.178.61.134 located?

Geolocation places 180.178.61.134 in Chiyoda City, Japan. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.

Is 180.178.61.134 on a blacklist?

Yes. 180.178.61.134 is currently listed by 4 threat sources: ThreatView High Confidence, FireHOL Level 2, Malicious IP (romainmarcoux), Data-Shield IPv4 Blocklist.

How do I report abuse from 180.178.61.134?

Send your log lines to the network's abuse contact, noc@netsec.com, 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/180.178.61.134

Guides for this IP