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

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

;; QUESTION SECTION:
;116.202.109.13.			IN	A

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

;; Query time: 63 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Feb 23 13:12:42 CST 2022
;; MSG SIZE  rcvd: 107
Host info
13.109.202.116.in-addr.arpa domain name pointer static.13.109.202.116.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
13.109.202.116.in-addr.arpa	name = static.13.109.202.116.clients.your-server.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
187.209.37.169 attackspam
[portscan] tcp/1433 [MsSQL]
in spfbl.net:'listed'
*(RWIN=8192)(10151156)
2019-10-16 00:49:04
196.203.31.154 attackbotsspam
Oct 15 18:17:07 vpn01 sshd[21518]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=196.203.31.154
Oct 15 18:17:09 vpn01 sshd[21518]: Failed password for invalid user ubuntu from 196.203.31.154 port 54383 ssh2
...
2019-10-16 00:19:14
13.126.205.13 attackspam
Oct 15 17:59:19 MK-Soft-VM3 sshd[11018]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.126.205.13 
Oct 15 17:59:21 MK-Soft-VM3 sshd[11018]: Failed password for invalid user tarmo from 13.126.205.13 port 57666 ssh2
...
2019-10-16 00:17:18
43.252.230.148 attackspambots
[portscan] tcp/1433 [MsSQL]
in spfbl.net:'listed'
*(RWIN=1024)(10151156)
2019-10-16 00:43:38
95.46.34.226 attack
[portscan] tcp/23 [TELNET]
in spfbl.net:'listed'
*(RWIN=12492)(10151156)
2019-10-16 00:36:30
183.129.160.229 attack
From CCTV User Interface Log
...::ffff:183.129.160.229 - - [15/Oct/2019:09:16:27 +0000] "GET / HTTP/1.1" 200 960
...
2019-10-16 00:22:30
62.213.82.18 attack
[portscan] tcp/1433 [MsSQL]
*(RWIN=1024)(10151156)
2019-10-16 00:40:41
37.6.244.94 attackspambots
[portscan] tcp/23 [TELNET]
in spfbl.net:'listed'
*(RWIN=29276)(10151156)
2019-10-16 00:44:59
113.160.1.70 attack
[portscan] tcp/1433 [MsSQL]
in sorbs:'listed [web]'
in spfbl.net:'listed'
*(RWIN=1024)(10151156)
2019-10-16 00:33:56
74.114.149.247 attackbots
[portscan] tcp/1433 [MsSQL]
*(RWIN=1024)(10151156)
2019-10-16 00:39:45
180.76.100.183 attack
$f2bV_matches
2019-10-16 00:10:36
101.22.30.68 attackbots
[portscan] tcp/23 [TELNET]
in spfbl.net:'listed'
*(RWIN=42770)(10151156)
2019-10-16 00:36:04
113.2.112.58 attackspambots
[portscan] tcp/23 [TELNET]
in SpamCop:'listed'
in spfbl.net:'listed'
in gbudb.net:'listed'
*(RWIN=52459)(10151156)
2019-10-16 00:34:15
122.147.42.2 attack
10/15/2019-12:00:33.862574 122.147.42.2 Protocol: 6 ET SCAN NMAP -sS window 1024
2019-10-16 00:32:38
221.204.232.87 attackbotsspam
[portscan] tcp/1433 [MsSQL]
in spfbl.net:'listed'
*(RWIN=1024)(10151156)
2019-10-16 00:46:22

Recently Reported IPs

116.202.104.81 116.20.21.19 116.202.112.139 116.199.170.17
116.202.117.253 116.202.120.148 116.202.128.245 116.202.118.150
116.202.130.199 116.202.127.202 116.202.131.113 116.202.131.194
116.202.134.107 116.202.135.148 116.202.156.186 116.202.157.61
116.202.16.149 116.202.16.153 116.202.17.245 116.202.180.41