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

;; QUESTION SECTION:
;160.252.139.2.			IN	A

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

;; Query time: 18 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 17 18:15:19 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 2.139.252.160.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 2.139.252.160.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.252.133.70 attack
Mar 18 20:42:54 sd-53420 sshd\[20995\]: Invalid user yang from 182.252.133.70
Mar 18 20:42:54 sd-53420 sshd\[20995\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.252.133.70
Mar 18 20:42:57 sd-53420 sshd\[20995\]: Failed password for invalid user yang from 182.252.133.70 port 39382 ssh2
Mar 18 20:48:30 sd-53420 sshd\[24888\]: User root from 182.252.133.70 not allowed because none of user's groups are listed in AllowGroups
Mar 18 20:48:30 sd-53420 sshd\[24888\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.252.133.70  user=root
...
2020-03-19 04:03:52
162.243.130.146 attackbotsspam
MultiHost/MultiPort Probe, Scan, Hack -
2020-03-19 03:50:37
175.207.12.52 attackspambots
SSH login attempts with user root.
2020-03-19 04:15:09
23.129.64.151 attackspam
Mar 18 18:50:55 meumeu sshd[28579]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.151 
Mar 18 18:50:56 meumeu sshd[28580]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=23.129.64.151 
...
2020-03-19 04:21:29
45.117.176.23 attackspambots
Mar 18 22:41:27 hosting sshd[13498]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.117.176.23  user=root
Mar 18 22:41:28 hosting sshd[13498]: Failed password for root from 45.117.176.23 port 48808 ssh2
Mar 18 22:46:06 hosting sshd[13952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.117.176.23  user=root
Mar 18 22:46:08 hosting sshd[13952]: Failed password for root from 45.117.176.23 port 54946 ssh2
...
2020-03-19 04:03:14
162.243.131.235 attackspambots
" "
2020-03-19 03:55:39
106.222.229.161 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-19 03:53:34
192.64.119.103 spam
AGAIN and AGAIN and ALWAYS the same REGISTRARS as namecheap.com, whoisguard.com, namesilo.com, privacyguardian.org and cloudflare.com TO STOP IMMEDIATELY for keeping SPAMMERS, LIERS, ROBERS and else since too many years ! The cheapest service, as usual...
And Link as usual by bit.ly to delette IMMEDIATELY too !
MARRE de ces ORDURES et autres FILS de PUTE genre SOUS MERDES capables de POLLUER STUPIDEMENT pour ne pas dire CONNEMENT la Planète par des POURRIELS INUTILES sur des listes VOLÉES on ne sait où et SANS notre accord !
mintmail.club => namecheap.com => whoisguard.com
mintmail.club => 192.64.119.103
192.64.119.103 => namecheap.com
https://www.mywot.com/scorecard/mintmail.club
https://www.mywot.com/scorecard/namecheap.com
https://www.mywot.com/scorecard/whoisguard.com
https://en.asytech.cn/check-ip/192.64.119.103
AS USUAL since few days for PHISHING and SCAM send to :
http://bit.ly/412dd15dd2 which resend to :
http://suggetat.com/r/ab857228-7ac2-4e29-8759-34786110318d/ which resend to :
https://enticingse.com/fr-carrefour/?s1=16T&s2=4044eb5b-28e9-425c-888f-4e092e7355e2&s3=&s4=&s5=&Fname=&Lname=&Email=#/0
suggetat.com => uniregistry.com
suggetat.com => 199.212.87.123
199.212.87.123 => hostwinds.com
enticingse.com => namesilo.com => privacyguardian.org
enticingse.com => 104.27.177.33
104.27.177.33 => cloudflare.com
namesilo.com => 104.17.175.85
privacyguardian.org => 2606:4700:20::681a:56 => cloudflare.com
https://www.mywot.com/scorecard/suggetat.com
https://www.mywot.com/scorecard/uniregistry.com
https://www.mywot.com/scorecard/hostwinds.com
https://www.mywot.com/scorecard/enticingse.com
https://www.mywot.com/scorecard/namesilo.com
https://www.mywot.com/scorecard/privacyguardian.org
https://www.mywot.com/scorecard/cloudflare.com
https://en.asytech.cn/check-ip/199.212.87.123
https://en.asytech.cn/check-ip/104.27.177.33
https://en.asytech.cn/check-ip/104.17.175.85
https://en.asytech.cn/check-ip/2606:4700:20::681a:56
2020-03-19 04:00:01
120.131.3.168 attack
Mar 18 14:43:06 lnxmail61 sshd[28325]: Failed password for root from 120.131.3.168 port 40978 ssh2
Mar 18 14:43:06 lnxmail61 sshd[28325]: Failed password for root from 120.131.3.168 port 40978 ssh2
2020-03-19 04:16:51
187.116.126.64 attack
$f2bV_matches
2020-03-19 04:00:37
151.80.61.70 attackspambots
Mar 18 18:45:05 sd-53420 sshd\[13683\]: Invalid user deployer from 151.80.61.70
Mar 18 18:45:05 sd-53420 sshd\[13683\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.61.70
Mar 18 18:45:07 sd-53420 sshd\[13683\]: Failed password for invalid user deployer from 151.80.61.70 port 46592 ssh2
Mar 18 18:49:08 sd-53420 sshd\[15052\]: Invalid user nsroot from 151.80.61.70
Mar 18 18:49:08 sd-53420 sshd\[15052\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=151.80.61.70
...
2020-03-19 03:51:45
106.52.44.85 attack
" "
2020-03-19 04:08:01
178.154.171.135 attackbots
[Thu Mar 19 01:09:05.922301 2020] [:error] [pid 22205:tid 139998025885440] [client 178.154.171.135:52227] [client 178.154.171.135] ModSecurity: Access denied with code 403 (phase 2). Pattern match "^[\\\\d.:]+$" at REQUEST_HEADERS:Host. [file "/etc/modsecurity/owasp-modsecurity-crs-3.2.0/rules/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "696"] [id "920350"] [msg "Host header is a numeric IP address"] [data "103.27.207.197"] [severity "WARNING"] [ver "OWASP_CRS/3.2.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "OWASP_CRS"] [tag "OWASP_CRS/PROTOCOL_VIOLATION/IP_HOST"] [tag "WASCTC/WASC-21"] [tag "OWASP_TOP_10/A7"] [tag "PCI/6.5.10"] [hostname "103.27.207.197"] [uri "/"] [unique_id "XnJjwYltBTtFXtqqFg2ZMwAAARY"]
...
2020-03-19 04:26:19
128.0.21.33 attack
Unauthorized connection attempt detected from IP address 128.0.21.33 to port 445
2020-03-19 04:05:27
181.63.248.149 attackbots
-
2020-03-19 04:04:24

Recently Reported IPs

84.148.53.122 17.183.177.98 148.80.141.128 248.2.32.175
62.146.205.238 132.233.204.122 48.233.17.11 206.34.42.165
123.96.76.98 201.207.28.179 6.5.143.123 202.172.39.206
179.211.113.168 198.7.8.88 127.51.249.167 116.197.5.24
108.3.155.58 224.5.251.186 230.137.1.72 38.14.127.131