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: Yongin-si

Region: Gyeonggi-do

Country: South Korea

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;122.40.5.142.			IN	A

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

;; Query time: 107 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun May 24 08:30:12 CST 2020
;; MSG SIZE  rcvd: 116
Host info
Host 142.5.40.122.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 142.5.40.122.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
77.232.128.87 attackbots
Nov 24 16:00:10 tux-35-217 sshd\[24808\]: Invalid user www from 77.232.128.87 port 34621
Nov 24 16:00:10 tux-35-217 sshd\[24808\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.232.128.87
Nov 24 16:00:12 tux-35-217 sshd\[24808\]: Failed password for invalid user www from 77.232.128.87 port 34621 ssh2
Nov 24 16:06:57 tux-35-217 sshd\[24832\]: Invalid user naim from 77.232.128.87 port 52396
Nov 24 16:06:57 tux-35-217 sshd\[24832\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.232.128.87
...
2019-11-24 23:12:07
118.70.190.188 attackspam
2019-11-24T14:57:05.537053abusebot-5.cloudsearch.cf sshd\[17622\]: Invalid user jrun from 118.70.190.188 port 38304
2019-11-24 23:04:56
27.17.118.148 attackbotsspam
port scan/probe/communication attempt; port 23
2019-11-24 23:01:41
94.191.120.164 attackbots
F2B jail: sshd. Time: 2019-11-24 15:56:49, Reported by: VKReport
2019-11-24 23:15:19
63.88.23.183 attack
63.88.23.183 was recorded 11 times by 7 hosts attempting to connect to the following ports: 80. Incident counter (4h, 24h, all-time): 11, 68, 581
2019-11-24 23:35:59
1.175.88.209 attackbotsspam
port scan/probe/communication attempt; port 23
2019-11-24 23:10:10
45.133.39.56 attackbotsspam
Email spam botnet
2019-11-24 22:58:24
167.172.242.160 attack
24.11.2019 15:03:18 SSH access blocked by firewall
2019-11-24 23:27:43
101.51.222.43 attackbots
Caught in portsentry honeypot
2019-11-24 23:32:00
118.24.221.190 attackbotsspam
Nov 24 04:49:15 hanapaa sshd\[1272\]: Invalid user tf2mgeserver from 118.24.221.190
Nov 24 04:49:15 hanapaa sshd\[1272\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.221.190
Nov 24 04:49:16 hanapaa sshd\[1272\]: Failed password for invalid user tf2mgeserver from 118.24.221.190 port 50911 ssh2
Nov 24 04:57:04 hanapaa sshd\[1904\]: Invalid user crutchfield from 118.24.221.190
Nov 24 04:57:04 hanapaa sshd\[1904\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=118.24.221.190
2019-11-24 23:06:49
138.68.94.173 attackspambots
$f2bV_matches
2019-11-24 23:03:34
192.144.148.163 attackbotsspam
Automatic report - Banned IP Access
2019-11-24 23:29:29
45.117.81.117 attack
45.117.81.117 - - \[24/Nov/2019:15:56:07 +0100\] "POST /wp-login.php HTTP/1.0" 200 5707 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
45.117.81.117 - - \[24/Nov/2019:15:56:09 +0100\] "POST /wp-login.php HTTP/1.0" 200 5707 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
45.117.81.117 - - \[24/Nov/2019:15:56:10 +0100\] "POST /xmlrpc.php HTTP/1.0" 200 802 "-" "Mozilla/5.0 \(X11\; Ubuntu\; Linux x86_64\; rv:62.0\) Gecko/20100101 Firefox/62.0"
2019-11-24 23:36:58
212.33.203.254 attack
212.33.203.254 was recorded 5 times by 1 hosts attempting to connect to the following ports: 9090,84. Incident counter (4h, 24h, all-time): 5, 5, 11
2019-11-24 23:21:50
181.114.155.233 attackspam
Caught in portsentry honeypot
2019-11-24 23:25:04

Recently Reported IPs

170.78.160.146 49.37.163.151 78.47.141.197 61.64.208.103
98.212.139.84 45.139.48.18 110.54.244.112 103.148.210.58
58.208.84.93 45.134.254.105 88.130.71.122 37.255.244.49
103.39.213.242 61.216.67.25 186.136.50.250 183.89.237.53
61.91.33.22 115.159.198.41 185.162.146.27 190.73.83.18