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

;; QUESTION SECTION:
;138.169.74.129.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Jan 26 03:29:11 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 129.74.169.138.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 129.74.169.138.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
45.122.221.42 attack
Invalid user castis from 45.122.221.42 port 53808
2019-10-17 21:39:55
197.47.87.55 attackspam
Telnet Server BruteForce Attack
2019-10-17 22:11:42
125.224.88.239 attackbotsspam
Telnet Server BruteForce Attack
2019-10-17 21:49:19
203.172.161.11 attackspam
SSH Brute-Forcing (ownc)
2019-10-17 21:48:57
159.65.102.98 attackspambots
WordPress login Brute force / Web App Attack on client site.
2019-10-17 22:19:36
59.46.189.242 attack
Unauthorised access (Oct 17) SRC=59.46.189.242 LEN=48 TOS=0x10 PREC=0x40 TTL=112 ID=12075 DF TCP DPT=445 WINDOW=8192 SYN
2019-10-17 22:18:59
177.23.196.77 attackbotsspam
2019-10-17T12:15:38.421976abusebot.cloudsearch.cf sshd\[21319\]: Invalid user marketing from 177.23.196.77 port 34244
2019-10-17 22:12:37
54.39.138.246 attackspambots
Oct 17 13:39:52 tuxlinux sshd[20033]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.138.246  user=root
Oct 17 13:39:55 tuxlinux sshd[20033]: Failed password for root from 54.39.138.246 port 41574 ssh2
Oct 17 13:39:52 tuxlinux sshd[20033]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=54.39.138.246  user=root
Oct 17 13:39:55 tuxlinux sshd[20033]: Failed password for root from 54.39.138.246 port 41574 ssh2
Oct 17 13:44:01 tuxlinux sshd[20088]: Invalid user roland from 54.39.138.246 port 57504
...
2019-10-17 21:51:26
222.186.175.182 attackbots
SSH-bruteforce attempts
2019-10-17 21:54:05
168.196.105.173 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-17 21:44:55
172.105.197.151 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-17 21:54:22
2.42.216.10 attack
Fail2Ban Ban Triggered
2019-10-17 21:58:05
172.105.210.107 attackspam
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-17 21:58:32
191.241.46.106 attackbots
Fail2Ban Ban Triggered
2019-10-17 22:18:19
121.137.77.82 attackspam
Oct 17 14:44:11 server sshd\[7995\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.137.77.82  user=root
Oct 17 14:44:14 server sshd\[7995\]: Failed password for root from 121.137.77.82 port 42836 ssh2
Oct 17 14:44:16 server sshd\[7995\]: Failed password for root from 121.137.77.82 port 42836 ssh2
Oct 17 14:44:17 server sshd\[7995\]: Failed password for root from 121.137.77.82 port 42836 ssh2
Oct 17 14:44:19 server sshd\[7995\]: Failed password for root from 121.137.77.82 port 42836 ssh2
...
2019-10-17 21:39:04

Recently Reported IPs

66.2.92.47 54.104.112.100 95.55.165.110 21.203.115.150
184.183.246.222 192.245.116.142 192.143.189.238 59.253.188.227
236.155.129.91 251.209.185.238 147.101.172.23 142.252.204.59
24.215.15.176 30.182.134.237 130.173.60.66 172.137.77.69
249.255.188.83 177.212.189.189 197.68.104.170 131.206.41.136