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

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

;; QUESTION SECTION:
;139.212.130.122.		IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 01:46:06 CST 2025
;; MSG SIZE  rcvd: 108
Host info
122.130.212.139.in-addr.arpa domain name pointer 122.130.212.139.adsl-pool.jlccptt.net.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
122.130.212.139.in-addr.arpa	name = 122.130.212.139.adsl-pool.jlccptt.net.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
168.121.71.14 attackbots
$f2bV_matches
2019-12-30 20:46:12
36.155.115.137 attackbotsspam
Dec 30 14:04:53 vps691689 sshd[26390]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=36.155.115.137
Dec 30 14:04:55 vps691689 sshd[26390]: Failed password for invalid user buddrus from 36.155.115.137 port 43978 ssh2
...
2019-12-30 21:22:04
213.234.26.179 attackbots
Dec 30 09:03:14 server sshd\[11114\]: Invalid user saldana from 213.234.26.179
Dec 30 09:03:14 server sshd\[11114\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ftp1.rlan.ru 
Dec 30 09:03:16 server sshd\[11114\]: Failed password for invalid user saldana from 213.234.26.179 port 51929 ssh2
Dec 30 09:22:04 server sshd\[15007\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=ftp1.rlan.ru  user=root
Dec 30 09:22:07 server sshd\[15007\]: Failed password for root from 213.234.26.179 port 36641 ssh2
...
2019-12-30 20:48:18
201.39.70.186 attackbotsspam
Unauthorized connection attempt detected from IP address 201.39.70.186 to port 22
2019-12-30 20:40:20
222.124.149.138 attackbotsspam
$f2bV_matches
2019-12-30 21:00:26
45.32.171.70 attack
Automatic report - XMLRPC Attack
2019-12-30 21:16:53
138.94.160.57 attack
Automatic report - Banned IP Access
2019-12-30 20:46:58
121.122.164.100 attackbotsspam
Unauthorized connection attempt detected from IP address 121.122.164.100 to port 8080
2019-12-30 20:55:51
134.17.94.229 attackspambots
Dec 30 12:45:20 xeon sshd[25421]: Failed password for mail from 134.17.94.229 port 2576 ssh2
2019-12-30 20:59:16
107.175.79.177 attack
(From eric@talkwithcustomer.com) Hello ehschiro.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website ehschiro.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website ehschiro.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing – as one famous marketer put it, “
2019-12-30 20:43:55
23.94.81.50 attackspambots
xmlrpc attack
2019-12-30 21:17:12
2.138.58.65 attackbotsspam
Dec 30 14:43:17 site3 sshd\[36063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.138.58.65  user=root
Dec 30 14:43:19 site3 sshd\[36063\]: Failed password for root from 2.138.58.65 port 33839 ssh2
Dec 30 14:47:56 site3 sshd\[36089\]: Invalid user kkariuki from 2.138.58.65
Dec 30 14:47:56 site3 sshd\[36089\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.138.58.65
Dec 30 14:47:58 site3 sshd\[36089\]: Failed password for invalid user kkariuki from 2.138.58.65 port 46971 ssh2
...
2019-12-30 20:57:46
152.115.62.241 attackspambots
19/12/30@01:21:17: FAIL: Alarm-Intrusion address from=152.115.62.241
...
2019-12-30 21:15:23
103.121.26.150 attackspambots
Invalid user forrest from 103.121.26.150 port 48965
2019-12-30 21:05:03
123.16.140.50 attackbotsspam
Lines containing failures of 123.16.140.50
Dec 30 07:21:01 MAKserver05 sshd[24956]: Invalid user admin from 123.16.140.50 port 52673
Dec 30 07:21:02 MAKserver05 sshd[24956]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.16.140.50 
Dec 30 07:21:04 MAKserver05 sshd[24956]: Failed password for invalid user admin from 123.16.140.50 port 52673 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=123.16.140.50
2019-12-30 20:55:11

Recently Reported IPs

54.69.160.234 96.153.66.25 121.116.70.123 191.67.174.182
180.47.178.200 175.235.132.95 222.6.14.95 171.44.231.42
244.202.30.102 57.155.87.195 243.115.239.22 206.77.193.109
88.185.126.248 155.250.195.105 232.241.100.11 222.159.67.226
216.128.182.87 134.34.35.111 29.239.110.181 165.178.94.193