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: Korea (the Republic of)

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

;; QUESTION SECTION:
;49.29.129.81.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 14 21:12:47 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 81.129.29.49.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 81.129.29.49.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
175.152.33.226 attackspambots
Port scan and direct access per IP instead of hostname
2019-07-28 15:49:54
171.36.133.8 attack
GET /index.asp HTTP/1.1
2019-07-28 15:55:41
77.221.146.10 attackbots
Jul 28 03:35:12 debian sshd\[7844\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.221.146.10  user=root
Jul 28 03:35:14 debian sshd\[7844\]: Failed password for root from 77.221.146.10 port 54884 ssh2
Jul 28 03:42:44 debian sshd\[7939\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=77.221.146.10  user=root
...
2019-07-28 16:31:11
186.31.65.66 attackbots
Jul 28 07:07:56 sshgateway sshd\[30321\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.31.65.66  user=root
Jul 28 07:07:58 sshgateway sshd\[30321\]: Failed password for root from 186.31.65.66 port 48945 ssh2
Jul 28 07:13:09 sshgateway sshd\[30349\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=186.31.65.66  user=root
2019-07-28 16:27:51
173.162.229.10 attack
Jul 28 08:39:49 MK-Soft-VM3 sshd\[26663\]: Invalid user 1QWERTY from 173.162.229.10 port 53226
Jul 28 08:39:49 MK-Soft-VM3 sshd\[26663\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.162.229.10
Jul 28 08:39:50 MK-Soft-VM3 sshd\[26663\]: Failed password for invalid user 1QWERTY from 173.162.229.10 port 53226 ssh2
...
2019-07-28 16:45:30
45.56.85.118 attackbots
[portscan] Port scan
2019-07-28 16:49:58
92.91.60.249 attackbotsspam
Jul 28 06:24:55 debian sshd\[16260\]: Invalid user lke from 92.91.60.249 port 57282
Jul 28 06:24:55 debian sshd\[16260\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.91.60.249
...
2019-07-28 16:28:43
139.162.146.15 attackbots
GET /api/v1/pods HTTP/1.1
2019-07-28 16:15:52
5.196.131.168 attackbots
Non-stop spam.
2019-07-28 16:10:56
218.75.36.70 attack
failed_logins
2019-07-28 16:09:57
141.105.102.155 attackbots
Port scan and direct access per IP instead of hostname
2019-07-28 16:12:49
139.162.119.197 attackspambots
Port scan and direct access per IP instead of hostname
2019-07-28 16:18:44
77.247.110.15 attackbots
" "
2019-07-28 16:52:35
63.83.73.134 attack
$f2bV_matches
2019-07-28 16:09:22
139.59.34.17 attackbotsspam
Jul 28 07:23:34 XXX sshd[7269]: Invalid user applmgr from 139.59.34.17 port 41486
2019-07-28 16:22:49

Recently Reported IPs

146.30.203.148 231.59.19.32 163.249.166.242 131.12.54.32
20.165.34.59 92.34.167.155 184.53.252.200 38.95.155.94
187.25.225.104 141.112.78.30 248.81.11.77 16.249.143.68
85.19.225.33 214.135.13.99 126.91.167.108 27.41.150.107
129.58.199.162 164.223.14.227 212.68.27.204 152.9.15.127