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 of America (the)

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

;; QUESTION SECTION:
;34.196.5.129.			IN	A

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

;; Query time: 194 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 06:56:56 CST 2025
;; MSG SIZE  rcvd: 105
Host info
129.5.196.34.in-addr.arpa domain name pointer ec2-34-196-5-129.compute-1.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
129.5.196.34.in-addr.arpa	name = ec2-34-196-5-129.compute-1.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
212.200.237.122 attackbots
NAME : TELEKOM-NET + e-mail abuse : abuse@telekom.rs CIDR : 212.200.236.0/23 | STATUS : 403 {Looking for resource vulnerabilities} DDoS Attack RS - block certain countries :) IP: 212.200.237.122  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-08-25 04:16:01
37.59.114.113 attack
2019-08-24T19:47:43.249333abusebot.cloudsearch.cf sshd\[872\]: Invalid user testuser from 37.59.114.113 port 41088
2019-08-25 03:49:41
183.105.217.170 attackbots
SSH invalid-user multiple login attempts
2019-08-25 04:20:11
58.91.235.17 attackspam
Unauthorised access (Aug 24) SRC=58.91.235.17 LEN=52 TOS=0x10 PREC=0x40 TTL=114 ID=28808 DF TCP DPT=445 WINDOW=8192 SYN
2019-08-25 04:08:09
137.59.162.169 attackbotsspam
Aug 24 21:56:25 * sshd[15609]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=137.59.162.169
Aug 24 21:56:27 * sshd[15609]: Failed password for invalid user dante from 137.59.162.169 port 41667 ssh2
2019-08-25 03:57:30
51.75.29.61 attackspambots
Aug 24 11:27:37 raspberrypi sshd\[29472\]: Invalid user blaze from 51.75.29.61Aug 24 11:27:39 raspberrypi sshd\[29472\]: Failed password for invalid user blaze from 51.75.29.61 port 45488 ssh2Aug 24 11:39:19 raspberrypi sshd\[29738\]: Invalid user duffy from 51.75.29.61Aug 24 11:39:21 raspberrypi sshd\[29738\]: Failed password for invalid user duffy from 51.75.29.61 port 47460 ssh2
...
2019-08-25 03:40:19
51.91.248.56 attackbotsspam
2019-08-24T23:28:16.736843enmeeting.mahidol.ac.th sshd\[5701\]: Invalid user chad from 51.91.248.56 port 47814
2019-08-24T23:28:16.755478enmeeting.mahidol.ac.th sshd\[5701\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=56.ip-51-91-248.eu
2019-08-24T23:28:18.640412enmeeting.mahidol.ac.th sshd\[5701\]: Failed password for invalid user chad from 51.91.248.56 port 47814 ssh2
...
2019-08-25 04:20:41
46.32.69.242 attack
Aug 24 21:51:58 localhost sshd\[28228\]: Invalid user password from 46.32.69.242 port 44077
Aug 24 21:51:58 localhost sshd\[28228\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.32.69.242
Aug 24 21:52:00 localhost sshd\[28228\]: Failed password for invalid user password from 46.32.69.242 port 44077 ssh2
2019-08-25 04:00:40
200.164.217.210 attackspam
Aug 24 19:30:31 XXX sshd[58997]: Invalid user testuser from 200.164.217.210 port 50383
2019-08-25 03:56:34
66.249.64.176 attackspambots
port scan and connect, tcp 80 (http)
2019-08-25 03:46:58
180.116.149.122 attackspam
Unauthorised access (Aug 24) SRC=180.116.149.122 LEN=40 TTL=49 ID=45048 TCP DPT=8080 WINDOW=54618 SYN 
Unauthorised access (Aug 24) SRC=180.116.149.122 LEN=40 TTL=49 ID=196 TCP DPT=8080 WINDOW=54618 SYN 
Unauthorised access (Aug 24) SRC=180.116.149.122 LEN=40 TTL=49 ID=36150 TCP DPT=8080 WINDOW=54618 SYN 
Unauthorised access (Aug 18) SRC=180.116.149.122 LEN=40 TTL=49 ID=23081 TCP DPT=8080 WINDOW=54618 SYN
2019-08-25 03:55:54
148.235.57.183 attack
Aug 24 20:54:19 tux-35-217 sshd\[15488\]: Invalid user bear123 from 148.235.57.183 port 40606
Aug 24 20:54:19 tux-35-217 sshd\[15488\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.235.57.183
Aug 24 20:54:21 tux-35-217 sshd\[15488\]: Failed password for invalid user bear123 from 148.235.57.183 port 40606 ssh2
Aug 24 20:59:04 tux-35-217 sshd\[15521\]: Invalid user 123123 from 148.235.57.183 port 34828
Aug 24 20:59:04 tux-35-217 sshd\[15521\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=148.235.57.183
...
2019-08-25 04:07:24
218.111.88.185 attackbotsspam
2019-08-24T15:54:45.151098abusebot-2.cloudsearch.cf sshd\[392\]: Invalid user mysql from 218.111.88.185 port 33260
2019-08-25 03:49:59
78.203.192.97 attackspam
/setup.cgi?next_file=netgear.cfg&todo=syscmd&cmd=busybox&curpath=/¤tsetting.htm=1
2019-08-25 03:51:31
190.52.128.8 attack
Invalid user zb from 190.52.128.8 port 36548
2019-08-25 03:43:44

Recently Reported IPs

52.97.252.234 44.111.140.220 248.169.216.235 52.149.59.246
152.246.34.125 250.99.199.37 26.250.83.237 108.213.97.47
204.102.152.31 62.229.8.121 47.123.217.151 40.186.134.25
161.77.182.162 251.13.89.127 210.51.226.57 75.80.46.20
205.54.26.154 179.70.105.119 160.160.158.234 22.9.16.42