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

;; QUESTION SECTION:
;3.29.104.185.			IN	A

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

;; Query time: 45 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jun 14 07:04:21 CST 2022
;; MSG SIZE  rcvd: 105
Host info
185.104.29.3.in-addr.arpa domain name pointer ec2-3-29-104-185.me-central-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
185.104.29.3.in-addr.arpa	name = ec2-3-29-104-185.me-central-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
94.23.33.22 attackbots
web-1 [ssh_2] SSH Attack
2020-09-23 00:43:05
189.112.123.157 attackbotsspam
Unauthorized connection attempt from IP address 189.112.123.157 on Port 445(SMB)
2020-09-23 00:38:51
118.103.117.159 attackspam
Unauthorized connection attempt from IP address 118.103.117.159 on Port 445(SMB)
2020-09-23 00:57:58
159.203.124.234 attackbotsspam
Sep 22 13:20:55 ws12vmsma01 sshd[4924]: Invalid user worker from 159.203.124.234
Sep 22 13:20:57 ws12vmsma01 sshd[4924]: Failed password for invalid user worker from 159.203.124.234 port 59582 ssh2
Sep 22 13:26:26 ws12vmsma01 sshd[5687]: Invalid user admin from 159.203.124.234
...
2020-09-23 00:57:11
185.156.73.64 attackspam
SSH Bruteforce Attempt on Honeypot
2020-09-23 00:46:46
141.98.82.20 attack
Sep 22 07:07:36    idslog syn_floodIN=eth4 OUT= SRC=141.98.82.20 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=123 PROTO=TCP SPT=65528 DPT=1234 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Sep 22 07:07:36    idslog syn_floodIN=eth4 OUT= SRC=141.98.82.20 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=123 PROTO=TCP SPT=65528 DPT=56740 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x800000
Sep 22 07:07:36    idslog syn_floodIN=eth4 OUT= SRC=141.98.82.20 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=123 PROTO=TCP SPT=65528 DPT=63392 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x800000
Sep 22 07:07:36    idslog syn_floodIN=eth4 OUT= SRC=141.98.82.20 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=123 PROTO=TCP SPT=65528 DPT=12021 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x800000
Sep 22 07:07:36    idslog syn_floodIN=eth4 OUT= SRC=141.98.82.20 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=123 PROTO=TCP SPT=65528 DPT=9001 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
2020-09-23 00:29:46
36.57.89.37 attack
Sep 21 22:39:14 srv01 postfix/smtpd\[3743\]: warning: unknown\[36.57.89.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 21 22:39:26 srv01 postfix/smtpd\[3743\]: warning: unknown\[36.57.89.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 21 22:39:42 srv01 postfix/smtpd\[3743\]: warning: unknown\[36.57.89.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 21 22:40:01 srv01 postfix/smtpd\[3743\]: warning: unknown\[36.57.89.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Sep 21 22:40:13 srv01 postfix/smtpd\[3743\]: warning: unknown\[36.57.89.37\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-09-23 00:43:24
139.59.136.99 attackbotsspam
Invalid user ubnt from 139.59.136.99 port 47440
2020-09-23 00:42:15
64.225.119.164 attackbots
$f2bV_matches
2020-09-23 00:56:50
191.255.232.53 attackspambots
Sep 22 13:55:21 vm2 sshd[29023]: Failed password for root from 191.255.232.53 port 46766 ssh2
Sep 22 15:00:05 vm2 sshd[29203]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=191.255.232.53
...
2020-09-23 00:44:09
193.227.16.160 attackspam
(sshd) Failed SSH login from 193.227.16.160 (EG/Egypt/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep 22 08:56:35 server sshd[5414]: Invalid user oracle from 193.227.16.160 port 58554
Sep 22 08:56:36 server sshd[5414]: Failed password for invalid user oracle from 193.227.16.160 port 58554 ssh2
Sep 22 09:03:56 server sshd[7379]: Invalid user ubuntu from 193.227.16.160 port 44540
Sep 22 09:03:59 server sshd[7379]: Failed password for invalid user ubuntu from 193.227.16.160 port 44540 ssh2
Sep 22 09:08:05 server sshd[8722]: Invalid user user from 193.227.16.160 port 53778
2020-09-23 01:08:21
187.188.206.106 attackspambots
Banned for a week because repeated abuses, for example SSH, but not only
2020-09-23 00:55:16
52.178.67.98 attack
CMS (WordPress or Joomla) login attempt.
2020-09-23 00:36:02
52.146.37.33 attackbotsspam
2020-09-21 UTC: (2x) - testftp(2x)
2020-09-23 00:48:50
87.110.181.30 attackspambots
$f2bV_matches
2020-09-23 00:46:30

Recently Reported IPs

3.36.33.3 3.78.252.97 3.74.197.190 3.35.165.14
3.65.192.211 3.56.205.156 3.56.20.70 3.56.64.213
3.56.75.205 3.57.143.246 45.71.202.45 107.152.223.186
144.168.151.126 200.60.60.60 200.7.10.158 3.80.82.9
3.80.180.180 3.71.61.217 3.44.61.41 3.53.83.210