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

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

;; QUESTION SECTION:
;142.92.97.104.			IN	A

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

;; Query time: 34 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 01 13:18:53 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 104.97.92.142.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 104.97.92.142.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
122.51.30.101 attackspambots
Feb  6 01:45:51 legacy sshd[5168]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.30.101
Feb  6 01:45:52 legacy sshd[5168]: Failed password for invalid user xpz from 122.51.30.101 port 45806 ssh2
Feb  6 01:49:33 legacy sshd[5409]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.30.101
...
2020-02-06 08:57:01
119.188.246.175 attack
2020-02-04T20:29:26.903039jupyter.data-analyst.biz sshd[8125]: Invalid user mikeh from 119.188.246.175 port 36449
2020-02-04T20:29:26.906008jupyter.data-analyst.biz sshd[8125]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.188.246.175
2020-02-04T20:29:26.903039jupyter.data-analyst.biz sshd[8125]: Invalid user mikeh from 119.188.246.175 port 36449
2020-02-04T20:29:28.435171jupyter.data-analyst.biz sshd[8125]: Failed password for invalid user mikeh from 119.188.246.175 port 36449 ssh2


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=119.188.246.175
2020-02-06 08:46:00
80.82.70.33 attackbots
Feb  6 01:44:53 debian-2gb-nbg1-2 kernel: \[3209139.486212\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=80.82.70.33 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=11067 PROTO=TCP SPT=55767 DPT=23467 WINDOW=1024 RES=0x00 SYN URGP=0
2020-02-06 09:01:05
61.95.233.61 attack
Unauthorized connection attempt detected from IP address 61.95.233.61 to port 2220 [J]
2020-02-06 08:41:52
149.56.141.193 attackbots
Unauthorized connection attempt detected from IP address 149.56.141.193 to port 2220 [J]
2020-02-06 09:04:06
62.234.61.180 attackspam
Unauthorized connection attempt detected from IP address 62.234.61.180 to port 2220 [J]
2020-02-06 09:11:12
188.254.0.2 attackbots
Fail2Ban - SSH Bruteforce Attempt
2020-02-06 08:43:57
107.189.11.168 attackspambots
Feb  5 23:23:39 ks10 sshd[2664597]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.189.11.168 
Feb  5 23:23:41 ks10 sshd[2664597]: Failed password for invalid user oeu from 107.189.11.168 port 41590 ssh2
...
2020-02-06 08:35:17
60.2.101.221 attackspambots
failed_logins
2020-02-06 08:54:05
80.82.64.134 attackbots
Feb  6 02:00:14 server sshd[64440]: Failed password for invalid user pi from 80.82.64.134 port 50171 ssh2
Feb  6 02:00:17 server sshd[64477]: Failed password for invalid user admin from 80.82.64.134 port 51549 ssh2
Feb  6 02:00:20 server sshd[64479]: Failed password for invalid user a from 80.82.64.134 port 53062 ssh2
2020-02-06 09:03:25
14.63.167.192 attackbotsspam
SSH Brute-Forcing (server2)
2020-02-06 08:51:11
140.143.17.156 attack
Feb  5 19:33:08 plusreed sshd[26032]: Invalid user djj from 140.143.17.156
...
2020-02-06 08:39:24
137.59.162.170 attackbotsspam
2020-02-05T18:55:12.8919481495-001 sshd[61236]: Invalid user rcy from 137.59.162.170 port 57815
2020-02-05T18:55:12.8953101495-001 sshd[61236]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.59.162.170
2020-02-05T18:55:12.8919481495-001 sshd[61236]: Invalid user rcy from 137.59.162.170 port 57815
2020-02-05T18:55:14.7476391495-001 sshd[61236]: Failed password for invalid user rcy from 137.59.162.170 port 57815 ssh2
2020-02-05T19:02:50.7873161495-001 sshd[62627]: Invalid user fii from 137.59.162.170 port 57778
2020-02-05T19:02:50.7965681495-001 sshd[62627]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.59.162.170
2020-02-05T19:02:50.7873161495-001 sshd[62627]: Invalid user fii from 137.59.162.170 port 57778
2020-02-05T19:02:52.8602441495-001 sshd[62627]: Failed password for invalid user fii from 137.59.162.170 port 57778 ssh2
2020-02-05T19:08:56.7776001495-001 sshd[63271]: Invalid user hut from 13
...
2020-02-06 08:53:24
163.172.90.3 attack
2020-02-06T00:25:06.837346micro sshd[3060]: Invalid user fake from 163.172.90.3 port 48596
2020-02-06T00:25:07.601927micro sshd[3062]: Invalid user admin from 163.172.90.3 port 50154
2020-02-06T00:25:09.131476micro sshd[3066]: Invalid user ubnt from 163.172.90.3 port 53058
2020-02-06T00:25:09.898135micro sshd[3068]: Invalid user guest from 163.172.90.3 port 54588
2020-02-06T00:25:10.651433micro sshd[3070]: Invalid user support from 163.172.90.3 port 55986
...
2020-02-06 08:42:13
120.194.198.44 attackbots
2020/02/05 23:22:40 \[error\] 1707\#1707: \*24916 limiting requests, excess: 0.325 by zone "one", client: 120.194.198.44, server: default_server, request: "GET /TP/index.php HTTP/1.1", host: "81.32.231.108"
...
2020-02-06 09:09:52

Recently Reported IPs

17.124.253.23 213.251.43.174 189.5.250.39 22.91.126.241
74.66.175.145 247.159.22.59 207.16.19.211 45.111.134.77
165.161.238.3 242.140.238.74 88.105.186.38 75.90.95.205
115.223.79.87 150.227.241.237 251.185.60.237 50.39.28.25
39.132.202.95 222.253.152.6 236.47.168.148 46.10.91.59