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: United States

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

;; QUESTION SECTION:
;104.20.92.146.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 14 18:39:31 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 146.92.20.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 146.92.20.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
149.154.157.188 attackbotsspam
[portscan] Port scan
2019-11-24 06:06:00
176.56.236.21 attackbotsspam
Nov 23 17:18:07 rotator sshd\[17585\]: Address 176.56.236.21 maps to alexjj.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Nov 23 17:18:09 rotator sshd\[17585\]: Failed password for sync from 176.56.236.21 port 42266 ssh2Nov 23 17:22:19 rotator sshd\[18352\]: Address 176.56.236.21 maps to alexjj.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Nov 23 17:22:19 rotator sshd\[18352\]: Invalid user bellet from 176.56.236.21Nov 23 17:22:20 rotator sshd\[18352\]: Failed password for invalid user bellet from 176.56.236.21 port 56816 ssh2Nov 23 17:25:37 rotator sshd\[19117\]: Address 176.56.236.21 maps to alexjj.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Nov 23 17:25:37 rotator sshd\[19117\]: Invalid user vcsa from 176.56.236.21
...
2019-11-24 06:10:50
192.34.62.227 attack
Nov 23 23:06:25 rotator sshd\[7602\]: Invalid user ekoinzynier from 192.34.62.227Nov 23 23:06:27 rotator sshd\[7602\]: Failed password for invalid user ekoinzynier from 192.34.62.227 port 40825 ssh2Nov 23 23:09:29 rotator sshd\[7628\]: Invalid user dwdevnet from 192.34.62.227Nov 23 23:09:32 rotator sshd\[7628\]: Failed password for invalid user dwdevnet from 192.34.62.227 port 43300 ssh2Nov 23 23:12:33 rotator sshd\[8392\]: Invalid user dwdev from 192.34.62.227Nov 23 23:12:35 rotator sshd\[8392\]: Failed password for invalid user dwdev from 192.34.62.227 port 45771 ssh2
...
2019-11-24 06:12:45
217.61.104.237 attack
SSH Brute-Force reported by Fail2Ban
2019-11-24 06:41:15
49.79.195.0 attackspambots
badbot
2019-11-24 06:18:33
60.2.99.126 attackbotsspam
(smtpauth) Failed SMTP AUTH login from 60.2.99.126 (CN/China/-): 5 in the last 3600 secs
2019-11-24 06:25:04
165.227.69.39 attackbotsspam
Nov 23 21:56:29 *** sshd[15644]: Failed password for invalid user training from 165.227.69.39 port 40882 ssh2
Nov 23 22:10:58 *** sshd[15903]: Failed password for invalid user webmaster from 165.227.69.39 port 43492 ssh2
Nov 23 22:14:02 *** sshd[15937]: Failed password for invalid user admin from 165.227.69.39 port 32943 ssh2
Nov 23 22:20:56 *** sshd[16037]: Failed password for invalid user nansen from 165.227.69.39 port 40082 ssh2
Nov 23 22:26:57 *** sshd[16183]: Failed password for invalid user operator from 165.227.69.39 port 47218 ssh2
Nov 23 22:33:19 *** sshd[16251]: Failed password for invalid user malvin from 165.227.69.39 port 54357 ssh2
Nov 23 22:36:23 *** sshd[16295]: Failed password for invalid user donnice from 165.227.69.39 port 43812 ssh2
Nov 23 22:39:24 *** sshd[16389]: Failed password for invalid user yoyo from 165.227.69.39 port 33268 ssh2
Nov 23 22:42:33 *** sshd[16473]: Failed password for invalid user rosseboe from 165.227.69.39 port 50956 ssh2
Nov 23 22:48:49 *** sshd[16586]: Failed passw
2019-11-24 06:17:12
81.28.100.121 attack
Nov 23 15:16:43  exim[1637]: [1\49] 1iYWDJ-0000QP-8a H=awake.shrewdmhealth.com (awake.exfundex.co) [81.28.100.121] F= rejected after DATA: This message scored 99.8 spam points.
2019-11-24 06:21:48
103.219.112.1 attackbots
Nov 23 06:37:14 hanapaa sshd\[17104\]: Invalid user mcwaters from 103.219.112.1
Nov 23 06:37:14 hanapaa sshd\[17104\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.1
Nov 23 06:37:16 hanapaa sshd\[17104\]: Failed password for invalid user mcwaters from 103.219.112.1 port 54904 ssh2
Nov 23 06:41:46 hanapaa sshd\[17544\]: Invalid user fbservice from 103.219.112.1
Nov 23 06:41:46 hanapaa sshd\[17544\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.219.112.1
2019-11-24 06:24:42
130.61.90.229 attackspam
Nov 23 19:42:35 localhost sshd\[28832\]: Invalid user carrico from 130.61.90.229 port 42632
Nov 23 19:42:35 localhost sshd\[28832\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=130.61.90.229
Nov 23 19:42:37 localhost sshd\[28832\]: Failed password for invalid user carrico from 130.61.90.229 port 42632 ssh2
...
2019-11-24 06:19:00
183.211.130.72 attackbots
badbot
2019-11-24 06:39:37
114.220.10.183 attack
Nov 23 23:16:02 mx1 postfix/smtpd\[9817\]: warning: unknown\[114.220.10.183\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6Nov 23 23:16:22 mx1 postfix/smtpd\[9817\]: warning: unknown\[114.220.10.183\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6Nov 23 23:16:49 mx1 postfix/smtpd\[9816\]: warning: unknown\[114.220.10.183\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2019-11-24 06:31:32
54.37.67.144 attack
2019-11-23T22:20:59.831441abusebot-7.cloudsearch.cf sshd\[8711\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.ip-54-37-67.eu  user=root
2019-11-24 06:38:26
120.84.205.60 attackbotsspam
badbot
2019-11-24 06:01:31
114.67.82.158 attackbotsspam
114.67.82.158 was recorded 103 times by 27 hosts attempting to connect to the following ports: 2375,2377,4243,2376. Incident counter (4h, 24h, all-time): 103, 328, 328
2019-11-24 06:28:20

Recently Reported IPs

104.20.9.32 104.20.93.146 104.20.97.110 104.20.98.110
104.20.99.110 104.200.133.138 104.200.140.67 104.200.146.166
104.200.170.40 104.200.20.47 104.200.21.162 104.200.23.143
104.200.24.102 104.200.24.204 104.200.25.125 104.200.31.196
183.242.240.96 104.200.31.230 104.206.134.86 104.206.229.210