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.134.245
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27847
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;137.226.134.245.		IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jun 26 17:14:14 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 245.134.226.137.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 245.134.226.137.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
46.38.144.202 attack
Jan 13 02:24:06 relay postfix/smtpd\[23464\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 13 02:24:16 relay postfix/smtpd\[30274\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 13 02:24:53 relay postfix/smtpd\[26394\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 13 02:25:01 relay postfix/smtpd\[31219\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Jan 13 02:25:41 relay postfix/smtpd\[26229\]: warning: unknown\[46.38.144.202\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-01-13 09:25:59
152.253.80.250 attackbotsspam
Jan 12 22:13:08 v32671 sshd[6764]: Address 152.253.80.250 maps to 152-253-80-250.user.vivozap.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Jan 12 22:13:08 v32671 sshd[6764]: Received disconnect from 152.253.80.250: 11: Bye Bye [preauth]
Jan 12 22:13:10 v32671 sshd[6766]: Address 152.253.80.250 maps to 152-253-80-250.user.vivozap.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Jan 12 22:13:11 v32671 sshd[6766]: Received disconnect from 152.253.80.250: 11: Bye Bye [preauth]
Jan 12 22:13:13 v32671 sshd[6768]: Address 152.253.80.250 maps to 152-253-80-250.user.vivozap.com.br, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Jan 12 22:13:13 v32671 sshd[6768]: Invalid user ubnt from 152.253.80.250
Jan 12 22:13:13 v32671 sshd[6768]: Received disconnect from 152.253.80.250: 11: Bye Bye [preauth]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=152.253.80.250
2020-01-13 09:12:09
129.154.67.65 attackbotsspam
Unauthorized connection attempt detected from IP address 129.154.67.65 to port 2220 [J]
2020-01-13 09:13:27
159.203.11.53 attackbots
Jan 13 01:59:03 vps58358 sshd\[30079\]: Invalid user libsys from 159.203.11.53Jan 13 01:59:05 vps58358 sshd\[30079\]: Failed password for invalid user libsys from 159.203.11.53 port 43788 ssh2Jan 13 02:02:28 vps58358 sshd\[30112\]: Invalid user oozie from 159.203.11.53Jan 13 02:02:30 vps58358 sshd\[30112\]: Failed password for invalid user oozie from 159.203.11.53 port 47424 ssh2Jan 13 02:05:49 vps58358 sshd\[30325\]: Invalid user sandy from 159.203.11.53Jan 13 02:05:51 vps58358 sshd\[30325\]: Failed password for invalid user sandy from 159.203.11.53 port 51130 ssh2
...
2020-01-13 09:18:24
87.197.126.24 attackbots
Jan 13 00:37:41 XXXXXX sshd[13882]: Invalid user user from 87.197.126.24 port 46324
2020-01-13 09:14:51
167.99.75.174 attackspam
Jan 13 01:15:17 flomail sshd[32175]: Invalid user dummy from 167.99.75.174
Jan 13 01:16:19 flomail sshd[32468]: Invalid user webmaster from 167.99.75.174
Jan 13 01:17:24 flomail sshd[32551]: Invalid user postgres from 167.99.75.174
2020-01-13 09:25:26
129.226.76.8 attackbots
Jan 13 01:14:19 server sshd\[24256\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.76.8  user=root
Jan 13 01:14:21 server sshd\[24256\]: Failed password for root from 129.226.76.8 port 45050 ssh2
Jan 13 01:36:07 server sshd\[29924\]: Invalid user svn from 129.226.76.8
Jan 13 01:36:07 server sshd\[29924\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=129.226.76.8 
Jan 13 01:36:09 server sshd\[29924\]: Failed password for invalid user svn from 129.226.76.8 port 34846 ssh2
...
2020-01-13 08:57:40
61.160.245.87 attackspam
Jan 13 02:57:30 docs sshd\[49861\]: Invalid user dev from 61.160.245.87Jan 13 02:57:31 docs sshd\[49861\]: Failed password for invalid user dev from 61.160.245.87 port 47616 ssh2Jan 13 03:00:09 docs sshd\[49904\]: Invalid user admin from 61.160.245.87Jan 13 03:00:12 docs sshd\[49904\]: Failed password for invalid user admin from 61.160.245.87 port 37888 ssh2Jan 13 03:02:55 docs sshd\[49942\]: Invalid user lea from 61.160.245.87Jan 13 03:02:57 docs sshd\[49942\]: Failed password for invalid user lea from 61.160.245.87 port 56394 ssh2
...
2020-01-13 09:03:58
178.23.151.66 attackbotsspam
Jan 12 17:24:23 server1 sshd\[14571\]: Failed password for invalid user odoo from 178.23.151.66 port 41754 ssh2
Jan 12 17:28:47 server1 sshd\[15725\]: Invalid user odoo from 178.23.151.66
Jan 12 17:28:47 server1 sshd\[15725\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.23.151.66 
Jan 12 17:28:48 server1 sshd\[15725\]: Failed password for invalid user odoo from 178.23.151.66 port 54161 ssh2
Jan 12 17:33:08 server1 sshd\[16799\]: Invalid user office from 178.23.151.66
...
2020-01-13 08:54:36
85.207.32.51 attack
Jan 13 03:48:16 hosting sshd[15880]: Invalid user connie from 85.207.32.51 port 42826
...
2020-01-13 09:12:49
223.71.167.163 attack
Unauthorized connection attempt detected from IP address 223.71.167.163 to port 3689 [T]
2020-01-13 09:00:04
91.228.32.4 attackbots
Automatic report - Port Scan Attack
2020-01-13 09:05:12
58.22.99.135 attackspambots
Jan 13 01:37:59 ks10 sshd[1574676]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.22.99.135 
Jan 13 01:38:01 ks10 sshd[1574676]: Failed password for invalid user david from 58.22.99.135 port 56670 ssh2
...
2020-01-13 09:10:48
49.88.112.62 attackspambots
Jan 12 15:05:59 web9 sshd\[13873\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.62  user=root
Jan 12 15:06:01 web9 sshd\[13873\]: Failed password for root from 49.88.112.62 port 50830 ssh2
Jan 12 15:06:18 web9 sshd\[13935\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.62  user=root
Jan 12 15:06:20 web9 sshd\[13935\]: Failed password for root from 49.88.112.62 port 13151 ssh2
Jan 12 15:06:45 web9 sshd\[13997\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.88.112.62  user=root
2020-01-13 09:17:59
168.121.71.14 attackbotsspam
Jan 13 00:26:31 vpn01 sshd[32533]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=168.121.71.14
Jan 13 00:26:33 vpn01 sshd[32533]: Failed password for invalid user steam from 168.121.71.14 port 54644 ssh2
...
2020-01-13 09:24:55

Recently Reported IPs

137.226.191.112 137.226.45.87 137.226.190.173 137.226.191.26
137.226.191.114 137.226.169.79 137.226.170.175 78.132.151.27
83.217.12.149 137.226.117.77 200.73.129.37 169.229.110.131
200.125.169.254 137.226.42.238 137.226.146.178 216.151.130.155
137.226.193.93 137.226.42.195 208.115.245.222 137.226.173.116