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: Hong Kong

Region: unknown

Country: Hong Kong

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:
#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#


NetRange:       45.139.136.0 - 45.150.51.255
CIDR:           45.140.0.0/14, 45.139.160.0/19, 45.150.48.0/22, 45.150.32.0/20, 45.144.0.0/14, 45.139.136.0/21, 45.148.0.0/15, 45.139.144.0/20, 45.139.192.0/18, 45.150.0.0/19
NetName:        RIPE
NetHandle:      NET-45-139-136-0-1
Parent:         NET45 (NET-45-0-0-0-0)
NetType:        Early Registrations, Transferred to RIPE NCC
OriginAS:       
Organization:   RIPE Network Coordination Centre (RIPE)
RegDate:        2014-05-22
Updated:        2025-04-14
Comment:        These addresses have been further assigned to users in the RIPE NCC region. Please note that the organization and point of contact details listed below are those of the RIPE NCC not the current address holder. ** You can find user contact information for the current address holder in the RIPE database at http://www.ripe.net/whois.
Ref:            https://rdap.arin.net/registry/ip/45.139.136.0

ResourceLink:  https://apps.db.ripe.net/db-web-ui/query
ResourceLink:  whois.ripe.net


OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:      
PostalCode:     1001EB
Country:        NL
RegDate:        
Updated:        2013-07-29
Ref:            https://rdap.arin.net/registry/entity/RIPE

ReferralServer:  whois.ripe.net
ResourceLink:  https://apps.db.ripe.net/db-web-ui/query

OrgAbuseHandle: ABUSE3850-ARIN
OrgAbuseName:   Abuse Contact
OrgAbusePhone:  +31205354444 
OrgAbuseEmail:  abuse@ripe.net
OrgAbuseRef:    https://rdap.arin.net/registry/entity/ABUSE3850-ARIN

OrgTechHandle: RNO29-ARIN
OrgTechName:   RIPE NCC Operations
OrgTechPhone:  +31 20 535 4444 
OrgTechEmail:  hostmaster@ripe.net
OrgTechRef:    https://rdap.arin.net/registry/entity/RNO29-ARIN


#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/resources/registry/whois/tou/
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/registry/whois/inaccuracy_reporting/
#
# Copyright 1997-2026, American Registry for Internet Numbers, Ltd.
#
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.142.154.60
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 38756
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.142.154.60.			IN	A

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

;; Query time: 6 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Mar 08 08:00:07 CST 2026
;; MSG SIZE  rcvd: 106
Host info
b'Host 60.154.142.45.in-addr.arpa not found: 2(SERVFAIL)
'
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 60.154.142.45.in-addr.arpa: SERVFAIL

Related IP info:
Related comments:
IP Type Details Datetime
201.217.58.113 attackspambots
Jul 16 06:50:26 bouncer sshd\[7501\]: Invalid user com1 from 201.217.58.113 port 52146
Jul 16 06:50:26 bouncer sshd\[7501\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.217.58.113 
Jul 16 06:50:28 bouncer sshd\[7501\]: Failed password for invalid user com1 from 201.217.58.113 port 52146 ssh2
...
2019-07-16 13:26:01
77.42.74.55 attackspambots
Automatic report - Port Scan Attack
2019-07-16 13:44:55
185.47.161.228 attackbots
Jul 16 03:35:31 cvbmail sshd\[19016\]: Invalid user luis from 185.47.161.228
Jul 16 03:35:31 cvbmail sshd\[19016\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.47.161.228
Jul 16 03:35:33 cvbmail sshd\[19016\]: Failed password for invalid user luis from 185.47.161.228 port 39042 ssh2
2019-07-16 13:29:30
188.166.237.191 attackbots
Invalid user mdom from 188.166.237.191 port 51694
2019-07-16 13:19:58
179.25.96.253 attack
MagicSpam Rule: block_rbl_lists (dyna.spamrats.com); Spammer IP: 179.25.96.253
2019-07-16 13:57:04
184.105.139.70 attackspam
Test report from splunk app
2019-07-16 13:46:31
187.44.1.206 attackspam
MagicSpam Rule: block_rbl_lists (spam.spamrats.com); Spammer IP: 187.44.1.206
2019-07-16 13:53:25
14.187.103.61 attackbotsspam
2019-07-16T01:35:58.602364abusebot.cloudsearch.cf sshd\[27433\]: Invalid user admin from 14.187.103.61 port 45195
2019-07-16 13:14:39
185.220.101.70 attackbotsspam
Jul 16 05:22:01 localhost sshd\[61429\]: Invalid user admin from 185.220.101.70 port 44709
Jul 16 05:22:01 localhost sshd\[61429\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=185.220.101.70
Jul 16 05:22:03 localhost sshd\[61429\]: Failed password for invalid user admin from 185.220.101.70 port 44709 ssh2
Jul 16 05:22:06 localhost sshd\[61429\]: Failed password for invalid user admin from 185.220.101.70 port 44709 ssh2
Jul 16 05:22:08 localhost sshd\[61429\]: Failed password for invalid user admin from 185.220.101.70 port 44709 ssh2
...
2019-07-16 13:54:26
185.132.127.152 attack
MagicSpam Rule: block_rbl_lists (zen.spamhaus.org); Spammer IP: 185.132.127.152
2019-07-16 13:48:24
195.254.135.76 attackbotsspam
2019-07-16T01:35:21.744586abusebot-3.cloudsearch.cf sshd\[3022\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=195.254.135.76  user=root
2019-07-16 13:36:08
115.94.231.12 attackspambots
Automatic report - SSH Brute-Force Attack
2019-07-16 13:26:58
35.205.169.134 attack
/wp-login.php
2019-07-16 12:58:08
5.9.40.211 attackbots
Jul 16 07:13:40 vps691689 sshd[25697]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=5.9.40.211
Jul 16 07:13:41 vps691689 sshd[25697]: Failed password for invalid user feng from 5.9.40.211 port 43824 ssh2
...
2019-07-16 13:36:29
188.128.39.131 attackbotsspam
Jul 16 01:26:08 vps200512 sshd\[27204\]: Invalid user admin1 from 188.128.39.131
Jul 16 01:26:08 vps200512 sshd\[27204\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.39.131
Jul 16 01:26:10 vps200512 sshd\[27204\]: Failed password for invalid user admin1 from 188.128.39.131 port 33490 ssh2
Jul 16 01:31:07 vps200512 sshd\[27276\]: Invalid user admin from 188.128.39.131
Jul 16 01:31:07 vps200512 sshd\[27276\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.128.39.131
2019-07-16 13:37:27

Recently Reported IPs

14.213.49.134 152.32.192.241 13.244.113.217 2606:4700:10::6814:6553
2606:4700:10::6814:6012 2606:4700:10::6814:6046 2606:4700:10::6814:9872 2606:4700:10::6814:9351
2606:4700:10::6814:8282 2606:4700:10::6816:2160 2606:4700:10::6814:5065 2606:4700:10::6814:8271
2606:4700:10::6814:7618 2606:4700:10::6814:5463 164.155.74.151 20.64.105.126
89.169.55.117 121.234.219.184 2606:4700:10::6814:5647 2606:4700:10::6814:6329