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: None

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

;; QUESTION SECTION:
;159.55.199.13.			IN	A

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

;; Query time: 36 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 11 20:46:43 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 13.199.55.159.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 13.199.55.159.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
69.60.21.172 attack
Bruteforce on SSH Honeypot
2019-06-21 20:03:15
178.239.148.9 attackspam
Unauthorised access (Jun 21) SRC=178.239.148.9 LEN=44 PREC=0x20 TTL=241 ID=13737 TCP DPT=445 WINDOW=1024 SYN
2019-06-21 19:48:14
157.122.116.160 attackspam
Jun 21 05:30:01 server1 sshd\[24514\]: Invalid user gang from 157.122.116.160
Jun 21 05:30:01 server1 sshd\[24514\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.122.116.160 
Jun 21 05:30:03 server1 sshd\[24514\]: Failed password for invalid user gang from 157.122.116.160 port 24572 ssh2
Jun 21 05:31:38 server1 sshd\[24949\]: Invalid user info from 157.122.116.160
Jun 21 05:31:38 server1 sshd\[24949\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.122.116.160 
...
2019-06-21 19:58:40
121.66.44.21 attackbotsspam
RDP
2019-06-21 20:39:16
223.74.180.193 attackbots
2019-06-21T11:19:35.658054 X postfix/smtpd[63799]: NOQUEUE: reject: RCPT from unknown[223.74.180.193]: 554 5.7.1 Service unavailable; Client host [223.74.180.193] blocked using zen.spamhaus.org; https://www.spamhaus.org/sbl/query/SBLCSS / https://www.spamhaus.org/query/ip/223.74.180.193; from= to= proto=ESMTP helo=
2019-06-21 19:47:41
185.137.111.136 attackbots
2019-06-21T16:27:40.659894ns1.unifynetsol.net postfix/smtpd\[32302\]: warning: unknown\[185.137.111.136\]: SASL LOGIN authentication failed: authentication failure
2019-06-21T16:28:04.590583ns1.unifynetsol.net postfix/smtpd\[468\]: warning: unknown\[185.137.111.136\]: SASL LOGIN authentication failed: authentication failure
2019-06-21T16:28:20.065872ns1.unifynetsol.net postfix/smtpd\[32124\]: warning: unknown\[185.137.111.136\]: SASL LOGIN authentication failed: authentication failure
2019-06-21T16:28:43.205596ns1.unifynetsol.net postfix/smtpd\[29770\]: warning: unknown\[185.137.111.136\]: SASL LOGIN authentication failed: authentication failure
2019-06-21T16:29:01.024906ns1.unifynetsol.net postfix/smtpd\[32124\]: warning: unknown\[185.137.111.136\]: SASL LOGIN authentication failed: authentication failure
2019-06-21 20:16:26
139.155.115.23 attackbots
SSH bruteforce (Triggered fail2ban)
2019-06-21 20:06:39
169.149.225.104 attackbotsspam
TCP port 445 (SMB) attempt blocked by firewall. [2019-06-21 11:16:12]
2019-06-21 20:22:57
65.70.31.19 attackspambots
DATE:2019-06-21 11:18:47, IP:65.70.31.19, PORT:telnet - Telnet brute force auth on a honeypot server (epe-dc)
2019-06-21 20:02:17
198.20.99.130 attackspam
Portscanning on different or same port(s).
2019-06-21 20:09:25
118.97.130.180 attackspambots
From CCTV User Interface Log
...::ffff:118.97.130.180 - - [21/Jun/2019:05:19:23 +0000] "GET / HTTP/1.1" 200 960
...
2019-06-21 19:49:45
60.169.94.134 attackbotsspam
TCP Port: 25 _    invalid blocked abuseat-org barracudacentral _  _  _ _ (332)
2019-06-21 19:55:50
41.42.114.150 attack
19/6/21@05:17:13: FAIL: IoT-SSH address from=41.42.114.150
...
2019-06-21 20:20:21
188.166.1.123 attack
Jun 21 14:09:38 web02 sshd\[37466\]: Invalid user db2inst2 from 188.166.1.123 port 34584
Jun 21 14:09:38 web02 sshd\[37467\]: Invalid user db2inst2 from 188.166.1.123 port 60910
...
2019-06-21 20:27:46
157.230.163.6 attackspambots
Feb 27 11:56:37 vtv3 sshd\[21065\]: Invalid user et from 157.230.163.6 port 37072
Feb 27 11:56:37 vtv3 sshd\[21065\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.163.6
Feb 27 11:56:39 vtv3 sshd\[21065\]: Failed password for invalid user et from 157.230.163.6 port 37072 ssh2
Feb 27 12:03:17 vtv3 sshd\[22954\]: Invalid user ir from 157.230.163.6 port 43692
Feb 27 12:03:17 vtv3 sshd\[22954\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.163.6
Feb 27 12:13:41 vtv3 sshd\[26105\]: Invalid user ji from 157.230.163.6 port 37768
Feb 27 12:13:41 vtv3 sshd\[26105\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=157.230.163.6
Feb 27 12:13:43 vtv3 sshd\[26105\]: Failed password for invalid user ji from 157.230.163.6 port 37768 ssh2
Feb 27 12:19:06 vtv3 sshd\[27752\]: Invalid user dm from 157.230.163.6 port 34804
Feb 27 12:19:06 vtv3 sshd\[27752\]: pam_unix\(sshd:auth\):
2019-06-21 20:00:16

Recently Reported IPs

38.120.84.120 50.203.60.239 139.248.175.178 154.35.92.56
241.43.247.216 50.230.74.198 206.117.55.210 53.110.19.105
129.77.255.206 160.95.203.207 72.90.9.133 217.252.90.54
132.13.227.151 89.150.234.21 247.151.85.236 163.54.132.255
164.241.209.140 66.18.143.48 75.158.210.246 53.234.183.130