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: South Korea

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

;; QUESTION SECTION:
;49.16.13.29.			IN	A

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

;; Query time: 43 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 13 10:30:47 CST 2025
;; MSG SIZE  rcvd: 104
Host info
Host 29.13.16.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 29.13.16.49.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
92.87.142.53 attackspambots
Fail2Ban Ban Triggered
2019-09-04 23:38:10
114.143.184.210 attackspambots
Sep  4 15:10:34 mintao sshd\[13864\]: Address 114.143.184.210 maps to static-210.184.143.114-tataidc.co.in, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!\
Sep  4 15:10:34 mintao sshd\[13864\]: Invalid user support from 114.143.184.210\
2019-09-04 23:10:20
114.141.104.45 attackbots
2019-09-04T13:48:19.235216abusebot-4.cloudsearch.cf sshd\[14621\]: Invalid user adminuser from 114.141.104.45 port 35137
2019-09-05 00:04:15
188.130.155.155 attackspam
Port 500/udp
2019-09-04 23:49:28
185.142.236.35 attackspam
Honeypot attack, port: 389, PTR: PTR record not found
2019-09-04 23:31:10
192.99.10.122 attackbots
09/04/2019-09:10:41.782510 192.99.10.122 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-09-04 23:03:09
103.114.107.129 attack
Unauthorised access (Sep  4) SRC=103.114.107.129 LEN=40 TTL=244 ID=1476 TCP DPT=3389 WINDOW=1024 SYN 
Unauthorised access (Sep  3) SRC=103.114.107.129 LEN=40 TTL=244 ID=57790 TCP DPT=3389 WINDOW=1024 SYN
2019-09-05 00:04:56
109.207.79.116 attackspam
Sep  4 05:21:23 php1 sshd\[7678\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.207.79.116  user=root
Sep  4 05:21:25 php1 sshd\[7678\]: Failed password for root from 109.207.79.116 port 57388 ssh2
Sep  4 05:26:17 php1 sshd\[8096\]: Invalid user ftptest from 109.207.79.116
Sep  4 05:26:17 php1 sshd\[8096\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=109.207.79.116
Sep  4 05:26:19 php1 sshd\[8096\]: Failed password for invalid user ftptest from 109.207.79.116 port 45576 ssh2
2019-09-04 23:37:44
106.52.156.219 attackbots
Sep  4 16:26:58 cp sshd[24169]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.52.156.219
2019-09-04 23:40:48
124.106.97.98 attackbots
445/tcp
[2019-09-04]1pkt
2019-09-04 23:00:06
201.69.200.201 attackbots
Sep  4 16:46:21 legacy sshd[25046]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.69.200.201
Sep  4 16:46:23 legacy sshd[25046]: Failed password for invalid user admins from 201.69.200.201 port 38745 ssh2
Sep  4 16:51:41 legacy sshd[25206]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.69.200.201
...
2019-09-04 23:23:34
220.121.58.55 attackbots
Sep  4 04:44:45 wbs sshd\[15401\]: Invalid user mpsingh from 220.121.58.55
Sep  4 04:44:45 wbs sshd\[15401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.121.58.55
Sep  4 04:44:47 wbs sshd\[15401\]: Failed password for invalid user mpsingh from 220.121.58.55 port 52248 ssh2
Sep  4 04:50:00 wbs sshd\[15871\]: Invalid user gerard from 220.121.58.55
Sep  4 04:50:00 wbs sshd\[15871\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=220.121.58.55
2019-09-04 23:01:16
165.22.125.61 attackbots
Sep  4 04:38:54 sachi sshd\[21651\]: Invalid user jeremy from 165.22.125.61
Sep  4 04:38:54 sachi sshd\[21651\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.125.61
Sep  4 04:38:56 sachi sshd\[21651\]: Failed password for invalid user jeremy from 165.22.125.61 port 50488 ssh2
Sep  4 04:43:34 sachi sshd\[22169\]: Invalid user admin from 165.22.125.61
Sep  4 04:43:34 sachi sshd\[22169\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=165.22.125.61
2019-09-04 22:53:27
151.80.144.255 attackbots
Sep  4 05:35:48 kapalua sshd\[3596\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=255.ip-151-80-144.eu  user=root
Sep  4 05:35:50 kapalua sshd\[3596\]: Failed password for root from 151.80.144.255 port 33108 ssh2
Sep  4 05:39:43 kapalua sshd\[4063\]: Invalid user wp from 151.80.144.255
Sep  4 05:39:43 kapalua sshd\[4063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=255.ip-151-80-144.eu
Sep  4 05:39:45 kapalua sshd\[4063\]: Failed password for invalid user wp from 151.80.144.255 port 54689 ssh2
2019-09-04 23:53:03
132.232.33.161 attack
Sep  4 16:50:24 xeon sshd[64840]: Failed password for root from 132.232.33.161 port 36280 ssh2
2019-09-04 23:05:03

Recently Reported IPs

185.10.121.177 133.230.206.4 30.1.106.204 72.185.19.85
244.162.195.168 228.212.63.202 46.130.204.102 223.19.111.33
109.247.47.30 176.113.115.189 206.134.25.184 86.211.152.236
32.205.179.226 204.155.105.139 223.88.26.10 225.245.218.114
210.166.30.85 44.217.85.12 45.183.238.39 245.250.167.48