Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: unknown

Region: unknown

Country: Germany

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 137.226.135.132
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 48838
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;137.226.135.132.		IN	A

;; AUTHORITY SECTION:
.			213	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2022061201 1800 900 604800 86400

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Jun 13 06:19:35 CST 2022
;; MSG SIZE  rcvd: 108
Host info
132.135.226.137.in-addr.arpa domain name pointer nb132.geo.rwth-aachen.de.
132.135.226.137.in-addr.arpa domain name pointer geo-132.geo.rwth-aachen.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
132.135.226.137.in-addr.arpa	name = nb132.geo.rwth-aachen.de.
132.135.226.137.in-addr.arpa	name = geo-132.geo.rwth-aachen.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
5.54.222.147 attack
Telnet Server BruteForce Attack
2019-11-04 03:13:09
45.226.81.197 attackbots
$f2bV_matches
2019-11-04 02:42:17
218.94.60.99 attack
11/03/2019-12:58:21.181144 218.94.60.99 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-11-04 03:15:50
162.241.129.247 attackspam
TELNET bruteforce
2019-11-04 02:55:52
54.37.196.144 attackbots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/54.37.196.144/ 
 
 FR - 1H : (66)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : FR 
 NAME ASN : ASN16276 
 
 IP : 54.37.196.144 
 
 CIDR : 54.37.0.0/16 
 
 PREFIX COUNT : 132 
 
 UNIQUE IP COUNT : 3052544 
 
 
 ATTACKS DETECTED ASN16276 :  
  1H - 3 
  3H - 7 
  6H - 17 
 12H - 22 
 24H - 40 
 
 DateTime : 2019-11-03 15:32:43 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-11-04 02:53:26
138.68.226.175 attack
Nov  3 21:06:28 server sshd\[27998\]: Invalid user odroid from 138.68.226.175
Nov  3 21:06:28 server sshd\[27998\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.226.175 
Nov  3 21:06:30 server sshd\[27998\]: Failed password for invalid user odroid from 138.68.226.175 port 46656 ssh2
Nov  3 21:13:42 server sshd\[29683\]: Invalid user test from 138.68.226.175
Nov  3 21:13:42 server sshd\[29683\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.68.226.175 
...
2019-11-04 03:06:04
141.255.106.110 attackspambots
Telnet/23 MH Probe, BF, Hack -
2019-11-04 02:43:35
123.21.94.145 attack
$f2bV_matches
2019-11-04 02:47:07
78.128.112.14 attackspambots
78.128.112.14 was recorded 21 times by 2 hosts attempting to connect to the following ports: 1212,33893,3399,1101,3396,5000,2005,23389,3400,10000,5050,2041,3383,33390,5557,8890,1976,3398,444,33890. Incident counter (4h, 24h, all-time): 21, 104, 251
2019-11-04 02:43:51
185.153.198.185 attackbots
Nov  3 11:03:22 TORMINT sshd\[3401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.153.198.185  user=root
Nov  3 11:03:24 TORMINT sshd\[3401\]: Failed password for root from 185.153.198.185 port 37982 ssh2
Nov  3 11:07:29 TORMINT sshd\[3971\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.153.198.185  user=root
...
2019-11-04 02:41:12
40.77.167.55 attackbotsspam
Forbidden directory scan :: 2019/11/03 14:32:22 [error] 63998#63998: *164191 access forbidden by rule, client: 40.77.167.55, server: [censored_1], request: "GET /... HTTP/1.1", host: "www.[censored_1]"
2019-11-04 03:08:36
159.89.162.118 attackbots
Nov  3 16:34:45 ArkNodeAT sshd\[27553\]: Invalid user postgresql from 159.89.162.118
Nov  3 16:34:45 ArkNodeAT sshd\[27553\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.89.162.118
Nov  3 16:34:46 ArkNodeAT sshd\[27553\]: Failed password for invalid user postgresql from 159.89.162.118 port 38630 ssh2
2019-11-04 03:13:59
178.68.232.248 attackbots
$f2bV_matches
2019-11-04 03:07:18
129.158.73.119 attackbots
2019-11-03T18:47:16.841645abusebot-3.cloudsearch.cf sshd\[19792\]: Invalid user wrangler from 129.158.73.119 port 52164
2019-11-04 03:14:59
118.91.255.14 attackbots
Brute force SMTP login attempted.
...
2019-11-04 02:47:29

Recently Reported IPs

137.226.133.157 137.226.135.123 137.226.135.217 137.226.135.251
137.226.136.94 137.226.137.53 137.226.137.118 137.226.137.200
137.226.137.251 137.226.138.33 137.226.138.103 137.226.138.143
137.226.138.197 137.226.72.64 169.229.238.183 137.226.114.168
137.226.114.191 137.226.120.195 169.229.232.203 137.226.91.86