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: Korea (the Republic of)

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:
IP Type Details Datetime
49.142.102.191 attackbotsspam
Telnet/23 MH Probe, Scan, BF, Hack -
2020-05-26 17:04:46
49.142.102.191 attack
Unauthorized connection attempt detected from IP address 49.142.102.191 to port 23 [J]
2020-01-29 10:37:40
49.142.102.191 attack
Unauthorized connection attempt detected from IP address 49.142.102.191 to port 23 [J]
2020-01-16 00:30:59
49.142.102.191 attackbots
Unauthorized connection attempt detected from IP address 49.142.102.191 to port 23 [T]
2020-01-09 16:30:02
49.142.102.191 attackbots
Unauthorized connection attempt detected from IP address 49.142.102.191 to port 23 [T]
2020-01-06 03:32:14
49.142.102.191 attack
Unauthorized connection attempt detected from IP address 49.142.102.191 to port 23
2020-01-03 20:37:34
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 49.142.102.10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62563
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;49.142.102.10.			IN	A

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

;; Query time: 37 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 22:54:03 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 10.102.142.49.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 10.102.142.49.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.222.84.34 attack
Oct 13 23:18:58 legacy sshd[1224]: Failed password for root from 92.222.84.34 port 55314 ssh2
Oct 13 23:22:38 legacy sshd[1324]: Failed password for root from 92.222.84.34 port 38320 ssh2
...
2019-10-14 05:37:28
222.186.15.204 attackspam
Fail2Ban Ban Triggered
2019-10-14 05:27:42
82.64.15.106 attack
SSH-bruteforce attempts
2019-10-14 05:04:11
41.87.80.26 attackspam
$f2bV_matches
2019-10-14 05:15:01
45.80.65.80 attackbots
Oct 13 22:57:47 legacy sshd[487]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.65.80
Oct 13 22:57:49 legacy sshd[487]: Failed password for invalid user P4$$W0RD123!@# from 45.80.65.80 port 37464 ssh2
Oct 13 23:03:49 legacy sshd[707]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.65.80
...
2019-10-14 05:07:07
158.174.78.94 attack
" "
2019-10-14 05:42:45
167.99.66.166 attackbotsspam
Sep  1 11:57:10 yesfletchmain sshd\[14072\]: User root from 167.99.66.166 not allowed because not listed in AllowUsers
Sep  1 11:57:11 yesfletchmain sshd\[14072\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.66.166  user=root
Sep  1 11:57:13 yesfletchmain sshd\[14072\]: Failed password for invalid user root from 167.99.66.166 port 43776 ssh2
Sep  1 12:03:25 yesfletchmain sshd\[14340\]: Invalid user test from 167.99.66.166 port 59078
Sep  1 12:03:25 yesfletchmain sshd\[14340\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.66.166
...
2019-10-14 05:37:48
185.90.116.200 attackbots
10/13/2019-16:58:48.508733 185.90.116.200 Protocol: 6 ET SCAN Potential SSH Scan
2019-10-14 05:15:45
121.35.96.224 attack
Telnetd brute force attack detected by fail2ban
2019-10-14 05:14:24
167.99.75.174 attack
Aug 21 23:08:48 yesfletchmain sshd\[26628\]: Invalid user clark from 167.99.75.174 port 51864
Aug 21 23:08:48 yesfletchmain sshd\[26628\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.174
Aug 21 23:08:50 yesfletchmain sshd\[26628\]: Failed password for invalid user clark from 167.99.75.174 port 51864 ssh2
Aug 21 23:14:47 yesfletchmain sshd\[26813\]: Invalid user xxx from 167.99.75.174 port 38938
Aug 21 23:14:47 yesfletchmain sshd\[26813\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.75.174
...
2019-10-14 05:26:37
167.99.54.4 attackbots
Feb 11 03:59:32 dillonfme sshd\[9518\]: Invalid user xw from 167.99.54.4 port 59128
Feb 11 03:59:32 dillonfme sshd\[9518\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.54.4
Feb 11 03:59:34 dillonfme sshd\[9518\]: Failed password for invalid user xw from 167.99.54.4 port 59128 ssh2
Feb 11 04:04:06 dillonfme sshd\[9582\]: Invalid user ubuntu from 167.99.54.4 port 50280
Feb 11 04:04:06 dillonfme sshd\[9582\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.54.4
...
2019-10-14 05:38:59
103.55.91.51 attack
Oct 13 23:11:48 vps647732 sshd[32317]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.55.91.51
Oct 13 23:11:51 vps647732 sshd[32317]: Failed password for invalid user Bacon@123 from 103.55.91.51 port 55070 ssh2
...
2019-10-14 05:37:08
217.243.172.58 attack
2019-10-13T16:11:02.822199ns525875 sshd\[8933\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.243.172.58  user=root
2019-10-13T16:11:04.810467ns525875 sshd\[8933\]: Failed password for root from 217.243.172.58 port 38702 ssh2
2019-10-13T16:15:16.993726ns525875 sshd\[14093\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.243.172.58  user=root
2019-10-13T16:15:18.850930ns525875 sshd\[14093\]: Failed password for root from 217.243.172.58 port 50306 ssh2
...
2019-10-14 05:33:32
222.186.180.223 attackbots
Oct 14 02:58:52 areeb-Workstation sshd[19425]: Failed password for root from 222.186.180.223 port 23054 ssh2
Oct 14 02:58:56 areeb-Workstation sshd[19425]: Failed password for root from 222.186.180.223 port 23054 ssh2
...
2019-10-14 05:39:41
27.50.176.189 attackbots
SSH invalid-user multiple login try
2019-10-14 05:30:09

Recently Reported IPs

175.251.104.209 72.62.220.238 133.47.156.132 188.217.198.43
2.80.3.223 187.15.134.171 147.218.88.67 91.149.175.2
109.190.119.240 95.1.236.54 98.127.248.20 173.156.219.222
171.209.170.210 166.193.172.73 180.69.30.58 196.226.94.65
42.39.185.42 129.237.204.107 230.158.93.169 193.174.165.92