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: Kawaguchi

Region: Saitama

Country: Japan

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

;; QUESTION SECTION:
;122.214.139.139.		IN	A

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

;; Query time: 57 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Apr 21 23:42:07 CST 2022
;; MSG SIZE  rcvd: 108
Host info
139.139.214.122.in-addr.arpa domain name pointer 122x214x139x139.ap122.ftth.ucom.ne.jp.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
139.139.214.122.in-addr.arpa	name = 122x214x139x139.ap122.ftth.ucom.ne.jp.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
41.226.28.41 attackspambots
SS1,DEF GET /wp-login.php
2019-09-24 16:41:01
128.199.107.252 attack
Sep 23 21:56:36 php1 sshd\[24812\]: Invalid user webadm from 128.199.107.252
Sep 23 21:56:36 php1 sshd\[24812\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.107.252
Sep 23 21:56:38 php1 sshd\[24812\]: Failed password for invalid user webadm from 128.199.107.252 port 55500 ssh2
Sep 23 22:05:31 php1 sshd\[25949\]: Invalid user mj from 128.199.107.252
Sep 23 22:05:31 php1 sshd\[25949\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.107.252
2019-09-24 16:16:50
222.186.190.92 attackspam
Sep 24 10:30:13 SilenceServices sshd[431]: Failed password for root from 222.186.190.92 port 37310 ssh2
Sep 24 10:30:18 SilenceServices sshd[431]: Failed password for root from 222.186.190.92 port 37310 ssh2
Sep 24 10:30:22 SilenceServices sshd[431]: Failed password for root from 222.186.190.92 port 37310 ssh2
Sep 24 10:30:26 SilenceServices sshd[431]: Failed password for root from 222.186.190.92 port 37310 ssh2
2019-09-24 16:41:52
211.54.40.81 attackbotsspam
Automatic report - Banned IP Access
2019-09-24 16:47:42
51.38.232.52 attackbots
Invalid user dujoey from 51.38.232.52 port 34299
2019-09-24 16:12:18
80.211.10.47 attackspambots
Sep 24 09:56:09 dedicated sshd[14449]: Invalid user jana from 80.211.10.47 port 28078
2019-09-24 16:15:08
186.212.190.28 attackspam
Automatic report - Port Scan Attack
2019-09-24 16:46:09
37.139.4.138 attack
Sep 24 06:48:53 site3 sshd\[24076\]: Invalid user yz from 37.139.4.138
Sep 24 06:48:53 site3 sshd\[24076\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.139.4.138
Sep 24 06:48:56 site3 sshd\[24076\]: Failed password for invalid user yz from 37.139.4.138 port 32947 ssh2
Sep 24 06:52:27 site3 sshd\[24160\]: Invalid user verwalter from 37.139.4.138
Sep 24 06:52:27 site3 sshd\[24160\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.139.4.138
...
2019-09-24 16:42:35
112.26.149.232 attackspambots
Unauthorised access (Sep 24) SRC=112.26.149.232 LEN=40 TOS=0x04 TTL=48 ID=47682 TCP DPT=8080 WINDOW=39686 SYN 
Unauthorised access (Sep 23) SRC=112.26.149.232 LEN=40 TOS=0x04 TTL=49 ID=48921 TCP DPT=8080 WINDOW=26595 SYN 
Unauthorised access (Sep 23) SRC=112.26.149.232 LEN=40 TOS=0x04 TTL=49 ID=36691 TCP DPT=8080 WINDOW=39686 SYN 
Unauthorised access (Sep 23) SRC=112.26.149.232 LEN=40 TOS=0x04 TTL=47 ID=42801 TCP DPT=8080 WINDOW=39686 SYN 
Unauthorised access (Sep 23) SRC=112.26.149.232 LEN=40 TOS=0x04 TTL=46 ID=36003 TCP DPT=8080 WINDOW=26595 SYN
2019-09-24 16:48:02
103.41.23.76 attackbots
Sep 24 03:43:38 ip-172-31-62-245 sshd\[2043\]: Invalid user service from 103.41.23.76\
Sep 24 03:43:40 ip-172-31-62-245 sshd\[2043\]: Failed password for invalid user service from 103.41.23.76 port 44354 ssh2\
Sep 24 03:48:25 ip-172-31-62-245 sshd\[2072\]: Invalid user jn from 103.41.23.76\
Sep 24 03:48:28 ip-172-31-62-245 sshd\[2072\]: Failed password for invalid user jn from 103.41.23.76 port 56788 ssh2\
Sep 24 03:53:07 ip-172-31-62-245 sshd\[2118\]: Invalid user eee from 103.41.23.76\
2019-09-24 16:19:08
106.12.85.12 attackbots
Sep 23 18:26:41 eddieflores sshd\[22477\]: Invalid user hdis_mng from 106.12.85.12
Sep 23 18:26:41 eddieflores sshd\[22477\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.85.12
Sep 23 18:26:43 eddieflores sshd\[22477\]: Failed password for invalid user hdis_mng from 106.12.85.12 port 56766 ssh2
Sep 23 18:32:18 eddieflores sshd\[22917\]: Invalid user ubnt from 106.12.85.12
Sep 23 18:32:18 eddieflores sshd\[22917\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.85.12
2019-09-24 16:09:42
34.73.55.203 attackbots
Sep 23 20:27:13 hiderm sshd\[4424\]: Invalid user yong from 34.73.55.203
Sep 23 20:27:13 hiderm sshd\[4424\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.55.73.34.bc.googleusercontent.com
Sep 23 20:27:15 hiderm sshd\[4424\]: Failed password for invalid user yong from 34.73.55.203 port 40470 ssh2
Sep 23 20:31:15 hiderm sshd\[4763\]: Invalid user titanium from 34.73.55.203
Sep 23 20:31:15 hiderm sshd\[4763\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.55.73.34.bc.googleusercontent.com
2019-09-24 16:22:08
49.143.95.121 attackbotsspam
[TueSep2405:52:27.1114172019][:error][pid26675:tid47560302733056][client49.143.95.121:44905][client49.143.95.121]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\\\\\\\\.sql\$"atREQUEST_FILENAME.[file"/etc/apache2/conf.d/modsec_rules/10_asl_rules.conf"][line"1288"][id"350590"][rev"2"][msg"Atomicorp.comWAFRules:AttackBlocked-Dataleakage-attempttoaccessrawSQLfiles\(disablethisruleifyourequireaccesstofilesthatendwith.sql\)"][severity"CRITICAL"][hostname"boltonholding.com"][uri"/boltonholding.sql"][unique_id"XYmS@yUY647fdT5XzKC6LAAAABU"][TueSep2405:52:29.4647092019][:error][pid26753:tid47560302733056][client49.143.95.121:45164][client49.143.95.121]ModSecurity:Accessdeniedwithcode403\(phase2\).Patternmatch"\\\\\\\\.sql\$"atREQUEST_FILENAME.[file"/etc/apache2/conf.d/modsec_rules/10_asl_rules.conf"][line"1288"][id"350590"][rev"2"][msg"Atomicorp.comWAFRules:AttackBlocked-Dataleakage-attempttoaccessrawSQLfiles\(disablethisruleifyourequireaccesstofilesthatendwith.sql\)"][sever
2019-09-24 16:41:30
149.202.56.194 attackspam
Sep 24 06:43:39 monocul sshd[19429]: Invalid user weblogic from 149.202.56.194 port 46934
...
2019-09-24 16:22:35
150.93.20.36 attackspambots
Sep 23 18:51:01 web9 sshd\[23752\]: Invalid user atn from 150.93.20.36
Sep 23 18:51:01 web9 sshd\[23752\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.93.20.36
Sep 23 18:51:03 web9 sshd\[23752\]: Failed password for invalid user atn from 150.93.20.36 port 45704 ssh2
Sep 23 18:55:38 web9 sshd\[24771\]: Invalid user yona from 150.93.20.36
Sep 23 18:55:38 web9 sshd\[24771\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=150.93.20.36
2019-09-24 16:26:32

Recently Reported IPs

172.104.167.126 102.109.226.203 246.245.250.113 131.84.221.238
239.242.59.23 164.28.123.140 128.165.220.226 219.173.218.44
171.115.127.255 113.204.54.224 206.171.209.199 238.187.38.255
143.174.236.20 250.13.255.254 5.42.85.113 26.55.7.230
34.101.120.115 213.170.220.27 12.185.199.122 30.21.188.71