IP abuse report43.225.68.34
43.225.68.34 is an IPv4 address located in Agra (Sanjay Place), India. It belongs to a network operated by U.P. COMMUNICATION SERVICES PVT LTD (AS59162). The address is listed by 5 of the threat-intelligence sources we track and carries a confidence score of 90/100. No community reports have been filed for it yet.
Provider notified This IP was reported to its network operator U.P. COMMUNICATION SERVICES PVT LTD · 2026-11-15 · IPDB-AR-007745 Awaiting reply Show detailsHide
- DetectedScore 90/100
- Notice sent2026-11-15 12:33
- Deliveredupinfomax.in
- Operator response Waiting · 4 days ago
The IP-DB Abuse Desk sent an abuse notice with supporting evidence to U.P. COMMUNICATION SERVICES PVT LTD's registered abuse contact on 2026-11-15 12:33: umesh@upinfomax.in
IP Information
- ISP / Organization
- U.P. COMMUNICATION SERVICES PVT LTD
- ASN
- AS59162 UPCSPL-AS-IN
- ASN Domain
- upcspl.in
- IP Range
- 43.225.68.0/22
- Regional Registry
- APNIC
- Connection Type
- Residential
- Country
- India (IN)
- Region / State
- Uttar Pradesh
- City
- Agra (Sanjay Place)
- Time Zone
- Unknown
- Abuse contact
- umesh@upinfomax.in 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
- 27.20, 78.01
- Network
- AS59162 U.P. COMMUNICATION SERVICES PVT LTD
The point is the city centre given by IP geolocation databases, not a street address. The circle shows the area of uncertainty.
Network Neighbourhood
43.225.68.0/24No other address in 43.225.68.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.
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.
When each feed first and last carried this address, over the last 30 days.
Blacklist Matches
5In our pool since: 2026-11-20 04:47 (1 hour ago) · Last confirmed: 2026-11-20 06:19
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Blocklist.de (all) | Single address | 2026-11-20 04:47 | 2026-11-20 06:1712 minutes ago |
| Data-Shield IPv4 Blocklist | Single address | 2026-11-20 06:19 | 2026-11-20 06:1910 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Blocklist.de Mail | Single address | 2026-11-20 04:47 | 2026-11-20 06:1712 minutes ago |
| Blocklist.de IMAP | Single address | 2026-11-20 04:49 | 2026-11-20 06:199 minutes ago |
| Source | Scope | First seen | Confirmed |
|---|---|---|---|
| Rutgers University DROP | Single address | 2026-11-20 04:47 | 2026-11-20 06:1711 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 43.225.68.34 login attempt root / ••••••
- 14:02:10 globalprotect:443 43.225.68.34 exploit attempt CVE-2024-3400
- 14:02:13 owa:4443 43.225.68.34 password spray Exchange OWA
- 14:02:16 netscaler:8443 43.225.68.34 Citrix Bleed scan CVE-2023-4966
- 14:02:20 ✓ evidence logged → added to your blocklist
Community Reports 0
Report This IPNo community reports yet for this IP.
Report This IPListing History
21The 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 43.225.68.34
Is 43.225.68.34 safe?
No. 43.225.68.34 scores 90/100 with strong, recent evidence of abuse (5 sources). Blocking it at your firewall is advisable.
Who owns 43.225.68.34?
43.225.68.34 is announced by AS59162 and operated by U.P. COMMUNICATION SERVICES PVT LTD. It sits in the 43.225.68.0/22 block registered with APNIC.
Where is 43.225.68.34 located?
Geolocation places 43.225.68.34 in Agra (Sanjay Place), India. IP geolocation is approximate: it shows where the network is registered or routed, not a device's street address.
Is 43.225.68.34 on a blacklist?
Yes. 43.225.68.34 is currently listed by 5 threat sources: Blocklist.de (all), Blocklist.de Mail, Rutgers University DROP, Data-Shield IPv4 Blocklist, Blocklist.de IMAP. DNS blacklists: 0 of 2 list it.
How do I report abuse from 43.225.68.34?
Send your log lines to the network's abuse contact, umesh@upinfomax.in, 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/43.225.68.34