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

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

;; QUESTION SECTION:
;217.12.147.116.			IN	A

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

;; Query time: 10 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jan 30 10:26:27 CST 2025
;; MSG SIZE  rcvd: 107
Host info
Host 116.147.12.217.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 116.147.12.217.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
185.36.81.78 attackspam
Mar 12 18:59:30 srv01 postfix/smtpd\[10340\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 19:04:41 srv01 postfix/smtpd\[27364\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 19:06:10 srv01 postfix/smtpd\[31767\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 19:06:43 srv01 postfix/smtpd\[31767\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar 12 19:11:29 srv01 postfix/smtpd\[32322\]: warning: unknown\[185.36.81.78\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-13 02:18:54
164.39.137.214 attackbots
Automatic report - Banned IP Access
2020-03-13 02:24:40
18.220.183.151 attack
Wordpress attack
2020-03-13 02:40:15
83.97.20.160 attackbotsspam
83.97.20.160 was recorded 5 times by 1 hosts attempting to connect to the following ports: 111. Incident counter (4h, 24h, all-time): 5, 13, 1065
2020-03-13 02:26:26
65.49.20.68 attack
2020-03-08T00:57:43.614Z CLOSE host=65.49.20.68 port=65106 fd=4 time=20.016 bytes=21
...
2020-03-13 02:14:52
45.147.228.41 attack
looking for open 25/tcp
2020-03-13 02:48:42
140.143.204.209 attackspam
port
2020-03-13 02:15:32
64.227.39.120 attackbotsspam
2020-02-24T19:24:38.430Z CLOSE host=64.227.39.120 port=58740 fd=4 time=20.009 bytes=20
...
2020-03-13 02:21:20
219.154.81.75 attackbotsspam
" "
2020-03-13 02:41:17
59.127.135.77 attack
2020-01-11T01:47:12.888Z CLOSE host=59.127.135.77 port=46050 fd=4 time=20.014 bytes=25
...
2020-03-13 02:48:11
61.133.238.106 attackbotsspam
Unauthorized connection attempt detected from IP address 61.133.238.106 to port 22 [T]
2020-03-13 02:42:55
182.61.182.58 attack
Fail2Ban - SSH Bruteforce Attempt
2020-03-13 02:39:20
5.34.131.72 attack
$f2bV_matches
2020-03-13 02:42:37
60.221.255.182 attack
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-03-13 02:47:49
77.40.58.102 attack
suspicious action Thu, 12 Mar 2020 09:29:22 -0300
2020-03-13 02:20:46

Recently Reported IPs

96.233.21.147 121.107.161.228 128.238.214.162 35.122.137.27
75.118.59.239 236.16.21.185 177.248.233.6 91.5.247.66
151.109.11.149 51.100.178.183 71.33.215.73 5.9.16.180
120.150.140.220 28.157.195.63 153.19.28.140 240.234.148.99
144.67.136.76 224.6.94.112 161.81.56.177 28.83.24.43