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: IANA Special-Purpose Address

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

;; QUESTION SECTION:
;249.155.198.13.			IN	A

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

;; Query time: 15 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Nov 17 17:44:43 CST 2024
;; MSG SIZE  rcvd: 107
Host info
Host 13.198.155.249.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.198.155.249.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
161.142.187.162 attackspam
Unauthorized connection attempt detected from IP address 161.142.187.162 to port 80 [J]
2020-01-20 18:44:24
111.230.144.232 attack
Jan 20 13:23:16 server sshd\[22485\]: Invalid user celka from 111.230.144.232
Jan 20 13:23:16 server sshd\[22485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.230.144.232 
Jan 20 13:23:19 server sshd\[22485\]: Failed password for invalid user celka from 111.230.144.232 port 44804 ssh2
Jan 20 13:35:19 server sshd\[25780\]: Invalid user ftpadmin from 111.230.144.232
Jan 20 13:35:19 server sshd\[25780\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.230.144.232 
...
2020-01-20 18:47:21
36.77.92.237 attack
Automatic report - FTP Brute Force
2020-01-20 18:33:32
1.53.19.239 attackspambots
Unauthorized connection attempt detected from IP address 1.53.19.239 to port 23 [J]
2020-01-20 18:35:21
174.92.78.57 attackbots
Unauthorized connection attempt detected from IP address 174.92.78.57 to port 5555 [J]
2020-01-20 18:19:53
221.202.203.192 attackspambots
Unauthorized connection attempt detected from IP address 221.202.203.192 to port 2220 [J]
2020-01-20 18:35:55
159.65.5.183 attackspam
Unauthorized connection attempt detected from IP address 159.65.5.183 to port 2220 [J]
2020-01-20 18:20:35
81.214.126.170 attackbots
Unauthorized connection attempt detected from IP address 81.214.126.170 to port 23 [J]
2020-01-20 18:14:23
188.138.184.130 attackspam
Unauthorized connection attempt detected from IP address 188.138.184.130 to port 23 [J]
2020-01-20 18:42:10
82.186.120.234 attackbots
Unauthorized connection attempt detected from IP address 82.186.120.234 to port 23 [J]
2020-01-20 18:27:31
200.53.20.108 attackspambots
Unauthorized connection attempt detected from IP address 200.53.20.108 to port 80 [J]
2020-01-20 18:39:22
170.106.36.56 attackspam
Unauthorized connection attempt detected from IP address 170.106.36.56 to port 102 [J]
2020-01-20 18:10:26
204.48.25.195 attack
Unauthorized connection attempt detected from IP address 204.48.25.195 to port 8080 [J]
2020-01-20 18:37:58
45.185.167.82 attack
" "
2020-01-20 18:32:37
125.239.30.71 attack
Unauthorized connection attempt detected from IP address 125.239.30.71 to port 9000 [J]
2020-01-20 18:11:55

Recently Reported IPs

49.154.208.175 134.6.161.104 35.173.181.33 255.179.146.49
163.81.101.191 128.124.168.54 134.106.182.85 147.102.103.95
63.129.39.16 38.199.10.75 224.55.254.251 252.233.46.55
198.162.55.132 32.212.109.127 144.128.187.34 31.10.70.129
199.34.217.151 23.48.217.154 224.10.191.215 92.128.89.76