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

;; QUESTION SECTION:
;139.129.155.154.		IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 27 12:32:52 CST 2022
;; MSG SIZE  rcvd: 108
Host info
Host 154.155.129.139.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 154.155.129.139.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
85.91.207.172 attackspambots
Unauthorized connection attempt from IP address 85.91.207.172 on Port 445(SMB)
2019-11-19 23:43:36
183.88.0.24 attack
Automatic report - Port Scan Attack
2019-11-20 00:07:08
77.225.216.136 attack
Fail2Ban Ban Triggered
2019-11-19 23:44:06
201.14.131.154 attack
LGS,WP GET /wp-login.php
2019-11-20 00:03:55
85.114.100.161 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/85.114.100.161/ 
 
 PS - 1H : (4)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : PS 
 NAME ASN : ASN42314 
 
 IP : 85.114.100.161 
 
 CIDR : 85.114.100.0/24 
 
 PREFIX COUNT : 40 
 
 UNIQUE IP COUNT : 10240 
 
 
 ATTACKS DETECTED ASN42314 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 1 
 
 DateTime : 2019-11-19 14:02:27 
 
 INFO : Port MAX SCAN Scan Detected and Blocked by ADMIN  - data recovery
2019-11-19 23:46:04
185.96.70.112 attack
" "
2019-11-20 00:06:46
157.55.39.132 attack
FakeBingbot
2019-11-20 00:05:03
196.44.202.122 attackbotsspam
Unauthorized connection attempt from IP address 196.44.202.122 on Port 445(SMB)
2019-11-19 23:50:50
171.240.98.188 attack
Nov 19 14:00:19 mxgate1 postfix/postscreen[7608]: CONNECT from [171.240.98.188]:21824 to [176.31.12.44]:25
Nov 19 14:00:19 mxgate1 postfix/dnsblog[7629]: addr 171.240.98.188 listed by domain cbl.abuseat.org as 127.0.0.2
Nov 19 14:00:19 mxgate1 postfix/dnsblog[7609]: addr 171.240.98.188 listed by domain zen.spamhaus.org as 127.0.0.4
Nov 19 14:00:19 mxgate1 postfix/dnsblog[7609]: addr 171.240.98.188 listed by domain zen.spamhaus.org as 127.0.0.3
Nov 19 14:00:19 mxgate1 postfix/dnsblog[7609]: addr 171.240.98.188 listed by domain zen.spamhaus.org as 127.0.0.11
Nov 19 14:00:20 mxgate1 postfix/dnsblog[7611]: addr 171.240.98.188 listed by domain b.barracudacentral.org as 127.0.0.2
Nov 19 14:00:25 mxgate1 postfix/postscreen[7608]: DNSBL rank 4 for [171.240.98.188]:21824
Nov x@x
Nov 19 14:00:27 mxgate1 postfix/postscreen[7608]: HANGUP after 2.2 from [171.240.98.188]:21824 in tests after SMTP handshake
Nov 19 14:00:27 mxgate1 postfix/postscreen[7608]: DISCONNECT [171.240.98.188]:........
-------------------------------
2019-11-19 23:47:25
188.254.0.183 attack
Nov 19 05:11:55 web1 sshd\[30237\]: Invalid user rynn from 188.254.0.183
Nov 19 05:11:55 web1 sshd\[30237\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.183
Nov 19 05:11:57 web1 sshd\[30237\]: Failed password for invalid user rynn from 188.254.0.183 port 56238 ssh2
Nov 19 05:15:57 web1 sshd\[30579\]: Invalid user guest from 188.254.0.183
Nov 19 05:15:57 web1 sshd\[30579\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.254.0.183
2019-11-19 23:55:51
190.198.75.60 attackspam
Unauthorized connection attempt from IP address 190.198.75.60 on Port 445(SMB)
2019-11-20 00:06:26
140.143.22.200 attack
2019-11-19T15:43:51.085094shield sshd\[5491\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.22.200  user=root
2019-11-19T15:43:53.255892shield sshd\[5491\]: Failed password for root from 140.143.22.200 port 34242 ssh2
2019-11-19T15:49:56.558316shield sshd\[6838\]: Invalid user bergsvendsen from 140.143.22.200 port 40912
2019-11-19T15:49:56.563263shield sshd\[6838\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.22.200
2019-11-19T15:49:58.507445shield sshd\[6838\]: Failed password for invalid user bergsvendsen from 140.143.22.200 port 40912 ssh2
2019-11-19 23:52:35
87.245.163.250 attack
postfix (unknown user, SPF fail or relay access denied)
2019-11-19 23:51:18
186.226.172.2 attackbots
186.226.172.2 was recorded 5 times by 2 hosts attempting to connect to the following ports: 8291. Incident counter (4h, 24h, all-time): 5, 5, 5
2019-11-20 00:01:25
193.106.49.18 attackspambots
Lines containing failures of 193.106.49.18
Nov 19 13:57:53 server01 postfix/smtpd[28070]: warning: hostname Pool-5-193.106.49.18.o.kg does not resolve to address 193.106.49.18: Name or service not known
Nov 19 13:57:53 server01 postfix/smtpd[28070]: connect from unknown[193.106.49.18]
Nov x@x
Nov x@x
Nov 19 13:57:54 server01 postfix/policy-spf[28075]: : Policy action=550 Please see hxxp://www.openspf.org/Why?s=mfrom;id=hbinfo%40iberhardware.com;ip=193.106.49.18;r=server01.2800km.de
Nov x@x
Nov 19 13:57:55 server01 postfix/smtpd[28070]: lost connection after DATA from unknown[193.106.49.18]
Nov 19 13:57:55 server01 postfix/smtpd[28070]: disconnect from unknown[193.106.49.18]


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=193.106.49.18
2019-11-19 23:35:14

Recently Reported IPs

139.129.154.146 31.185.16.113 246.24.122.178 145.220.109.237
139.129.157.36 139.129.156.132 139.129.156.102 139.129.155.227
139.129.156.122 139.129.157.118 139.129.157.200 139.129.156.225
139.129.156.22 139.129.156.119 139.129.156.18 139.129.156.2
168.159.126.183 139.129.157.8 139.129.157.81 139.129.158.166