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: United States

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

;; QUESTION SECTION:
;13.245.42.107.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 28 05:54:21 CST 2022
;; MSG SIZE  rcvd: 106
Host info
107.42.245.13.in-addr.arpa domain name pointer ec2-13-245-42-107.af-south-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
107.42.245.13.in-addr.arpa	name = ec2-13-245-42-107.af-south-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
190.109.168.18 attackspambots
Apr 30 06:11:37 server sshd\[138860\]: Invalid user admin1 from 190.109.168.18
Apr 30 06:11:37 server sshd\[138860\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.109.168.18
Apr 30 06:11:39 server sshd\[138860\]: Failed password for invalid user admin1 from 190.109.168.18 port 58979 ssh2
...
2019-08-01 06:47:04
137.74.194.226 attackspambots
Aug  1 00:33:58 MK-Soft-Root1 sshd\[28137\]: Invalid user isar from 137.74.194.226 port 37012
Aug  1 00:33:58 MK-Soft-Root1 sshd\[28137\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.74.194.226
Aug  1 00:33:59 MK-Soft-Root1 sshd\[28137\]: Failed password for invalid user isar from 137.74.194.226 port 37012 ssh2
...
2019-08-01 06:48:51
81.26.66.36 attackbots
2019-07-31T21:58:31.457457abusebot-2.cloudsearch.cf sshd\[14470\]: Invalid user cku from 81.26.66.36 port 50532
2019-08-01 06:07:06
178.62.33.38 attackbotsspam
Jul 31 20:31:06 MK-Soft-VM7 sshd\[19196\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.33.38  user=bin
Jul 31 20:31:08 MK-Soft-VM7 sshd\[19196\]: Failed password for bin from 178.62.33.38 port 49076 ssh2
Jul 31 20:35:20 MK-Soft-VM7 sshd\[19201\]: Invalid user webmaster from 178.62.33.38 port 44626
Jul 31 20:35:20 MK-Soft-VM7 sshd\[19201\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.62.33.38
...
2019-08-01 06:42:18
156.224.129.127 attackspam
Jul 31 20:31:22 mxgate1 postfix/postscreen[3428]: CONNECT from [156.224.129.127]:49086 to [176.31.12.44]:25
Jul 31 20:31:22 mxgate1 postfix/dnsblog[3449]: addr 156.224.129.127 listed by domain zen.spamhaus.org as 127.0.0.3
Jul 31 20:31:28 mxgate1 postfix/postscreen[3428]: DNSBL rank 2 for [156.224.129.127]:49086
Jul x@x
Jul 31 20:31:29 mxgate1 postfix/postscreen[3428]: DISCONNECT [156.224.129.127]:49086


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=156.224.129.127
2019-08-01 06:26:43
190.111.232.7 attack
Jun  8 22:29:18 server sshd\[90772\]: Invalid user pi from 190.111.232.7
Jun  8 22:29:18 server sshd\[90770\]: Invalid user pi from 190.111.232.7
Jun  8 22:29:18 server sshd\[90772\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.111.232.7
Jun  8 22:29:18 server sshd\[90770\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.111.232.7
Jun  8 22:29:19 server sshd\[90772\]: Failed password for invalid user pi from 190.111.232.7 port 53800 ssh2
Jun  8 22:29:19 server sshd\[90770\]: Failed password for invalid user pi from 190.111.232.7 port 53796 ssh2
...
2019-08-01 06:33:05
60.53.38.134 attack
Lines containing failures of 60.53.38.134


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=60.53.38.134
2019-08-01 06:09:50
36.69.109.51 attackspambots
Jul 31 20:26:09 server658 sshd[1256]: Did not receive identification string from 36.69.109.51
Jul 31 20:27:33 server658 sshd[1279]: Invalid user thostname0nich from 36.69.109.51


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=36.69.109.51
2019-08-01 06:05:13
177.11.117.97 attack
libpam_shield report: forced login attempt
2019-08-01 06:22:35
92.63.194.90 attackbots
Aug  1 02:07:33 areeb-Workstation sshd\[8352\]: Invalid user admin from 92.63.194.90
Aug  1 02:07:33 areeb-Workstation sshd\[8352\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.63.194.90
Aug  1 02:07:35 areeb-Workstation sshd\[8352\]: Failed password for invalid user admin from 92.63.194.90 port 32770 ssh2
...
2019-08-01 06:36:59
190.114.255.120 attackbots
Jul 26 09:31:44 dallas01 sshd[18934]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.114.255.120
Jul 26 09:31:45 dallas01 sshd[18934]: Failed password for invalid user hua from 190.114.255.120 port 59924 ssh2
Jul 26 09:37:31 dallas01 sshd[19754]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=190.114.255.120
2019-08-01 06:10:25
121.201.34.97 attackspambots
Jun 13 21:10:44 server sshd\[119470\]: Invalid user guest from 121.201.34.97
Jun 13 21:10:44 server sshd\[119470\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.201.34.97
Jun 13 21:10:46 server sshd\[119470\]: Failed password for invalid user guest from 121.201.34.97 port 58084 ssh2
...
2019-08-01 06:12:30
31.146.61.142 attackbotsspam
Jul 31 20:39:30 h2022099 sshd[1356]: Did not receive identification string from 31.146.61.142
Jul 31 20:39:31 h2022099 sshd[1357]: reveeclipse mapping checking getaddrinfo for 31-146-61-142.dsl.utg.ge [31.146.61.142] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul 31 20:39:31 h2022099 sshd[1357]: Invalid user ubnt from 31.146.61.142
Jul 31 20:39:31 h2022099 sshd[1357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=31.146.61.142 
Jul 31 20:39:33 h2022099 sshd[1357]: Failed password for invalid user ubnt from 31.146.61.142 port 62340 ssh2
Jul 31 20:39:37 h2022099 sshd[1357]: Connection closed by 31.146.61.142 [preauth]
Jul 31 20:39:38 h2022099 sshd[1387]: reveeclipse mapping checking getaddrinfo for 31-146-61-142.dsl.utg.ge [31.146.61.142] failed - POSSIBLE BREAK-IN ATTEMPT!
Jul 31 20:39:38 h2022099 sshd[1387]: Invalid user UBNT from 31.146.61.142
Jul 31 20:39:38 h2022099 sshd[1387]: pam_unix(sshd:auth): authentication failure; logname= u........
-------------------------------
2019-08-01 06:42:51
187.120.133.206 attackspam
libpam_shield report: forced login attempt
2019-08-01 06:43:39
45.83.67.133 attack
" "
2019-08-01 06:12:15

Recently Reported IPs

13.248.131.126 13.248.128.131 13.248.136.124 13.246.65.127
13.248.135.84 13.248.136.71 13.248.138.16 13.248.142.135
13.248.138.46 13.248.139.164 13.248.143.202 13.248.182.197
13.248.145.31 13.248.149.249 13.248.146.247 13.248.179.47
13.224.195.9 13.224.195.61 13.224.195.76 13.213.223.140