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

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

;; QUESTION SECTION:
;95.216.49.14.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 24 16:44:51 CST 2023
;; MSG SIZE  rcvd: 105
Host info
14.49.216.95.in-addr.arpa domain name pointer static.14.49.216.95.clients.your-server.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

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

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
46.173.211.87 attack
spam 08 Oct 2020 02:29 Received: from mail.golinska.de ([46.173.211.87])
2020-10-09 03:45:25
112.85.42.120 attackspambots
(sshd) Failed SSH login from 112.85.42.120 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  8 15:46:08 optimus sshd[10864]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.120  user=root
Oct  8 15:46:08 optimus sshd[10860]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.120  user=root
Oct  8 15:46:08 optimus sshd[10861]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.120  user=root
Oct  8 15:46:08 optimus sshd[10857]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.120  user=root
Oct  8 15:46:08 optimus sshd[10854]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.85.42.120  user=root
2020-10-09 03:56:41
185.191.171.13 attack
[Thu Oct 08 22:45:50.402043 2020] [:error] [pid 4934:tid 140205054985984] [client 185.191.171.13:56010] [client 185.191.171.13] ModSecurity: Access denied with code 403 (phase 2). Matched phrase "SemrushBot" at REQUEST_HEADERS:User-Agent. [file "/etc/modsecurity/coreruleset-3.3.0/rules/REQUEST-913-SCANNER-DETECTION.conf"] [line "181"] [id "913102"] [msg "Found User-Agent associated with web crawler/bot"] [data "Matched Data: SemrushBot found within REQUEST_HEADERS:User-Agent: mozilla/5.0 (compatible; semrushbot/6~bl; +http://www.semrush.com/bot.html)"] [severity "CRITICAL"] [ver "OWASP_CRS/3.3.0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-reputation-crawler"] [tag "OWASP_CRS"] [tag "capec/1000/118/224/541/310"] [tag "PCI/6.5.10"] [tag "paranoia-level/2"] [hostname "karangploso.jatim.bmkg.go.id"] [uri "/index.php/prakiraan-iklim/prakiraan-dasarian/prakiraan-dasarian-daerah-potensi-banjir/555558184-prakiraan-dasarian-daerah-potensi-banjir-di-pro
...
2020-10-09 03:49:34
49.235.132.88 attack
Oct  8 21:18:29 vps639187 sshd\[21077\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.132.88  user=root
Oct  8 21:18:31 vps639187 sshd\[21077\]: Failed password for root from 49.235.132.88 port 57108 ssh2
Oct  8 21:24:08 vps639187 sshd\[21133\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.132.88  user=root
...
2020-10-09 03:27:30
159.203.172.159 attack
(sshd) Failed SSH login from 159.203.172.159 (US/United States/haliupdates.com): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct  8 15:04:47 optimus sshd[27276]: Failed password for root from 159.203.172.159 port 41882 ssh2
Oct  8 15:12:53 optimus sshd[30572]: Failed password for root from 159.203.172.159 port 57966 ssh2
Oct  8 15:16:05 optimus sshd[31794]: Failed password for root from 159.203.172.159 port 35326 ssh2
Oct  8 15:19:16 optimus sshd[696]: Invalid user testtest from 159.203.172.159
Oct  8 15:19:19 optimus sshd[696]: Failed password for invalid user testtest from 159.203.172.159 port 40962 ssh2
2020-10-09 03:58:05
220.173.167.164 attackbots
1433/tcp 1433/tcp
[2020-10-07]2pkt
2020-10-09 03:53:52
112.85.42.194 attackbotsspam
Oct  8 17:56:37 vm0 sshd[10913]: Failed password for root from 112.85.42.194 port 55590 ssh2
...
2020-10-09 03:59:47
61.143.152.4 attackbots
IP 61.143.152.4 attacked honeypot on port: 1433 at 10/7/2020 1:39:56 PM
2020-10-09 03:32:53
183.90.253.37 attackbots
uvcm 183.90.253.37 [07/Oct/2020:21:55:46 "-" "POST /wp-login.php 200 3356
183.90.253.37 [08/Oct/2020:03:36:33 "-" "GET /wp-login.php 200 3235
183.90.253.37 [08/Oct/2020:03:36:34 "-" "POST /wp-login.php 200 3356
2020-10-09 03:52:59
45.135.232.39 attackbotsspam
Port Scan: TCP/3389
2020-10-09 03:45:43
116.255.190.176 attackbots
Port scan denied
2020-10-09 03:43:46
63.240.240.74 attackspam
Cluster member 178.17.174.160 (MD/Republic of Moldova/Chișinău Municipality/Chisinau/kiv.hlex.pw/[AS43289 I.C.S. Trabia-Network S.R.L.]) said, TEMPDENY 63.240.240.74, Reason:[(sshd) Failed SSH login from 63.240.240.74 (US/United States/Florida/Miami/-/[AS16959 SBIS-AMRLTX]): 1 in the last 3600 secs]; Ports: *; Direction: inout; Trigger: LF_CLUSTER; Logs:
2020-10-09 03:32:38
162.243.237.90 attack
Oct  8 21:33:28 itv-usvr-01 sshd[4306]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=162.243.237.90  user=root
Oct  8 21:33:30 itv-usvr-01 sshd[4306]: Failed password for root from 162.243.237.90 port 43527 ssh2
2020-10-09 03:27:55
27.77.234.82 attackbots
20/10/8@08:43:11: FAIL: IoT-Telnet address from=27.77.234.82
...
2020-10-09 03:51:37
171.232.112.14 attackspambots
Telnet Server BruteForce Attack
2020-10-09 03:55:46

Recently Reported IPs

39.96.105.228 0.232.10.170 217.107.73.250 94.227.50.125
178.89.172.132 102.99.47.137 190.252.144.242 81.28.152.75
43.239.58.167 80.235.74.250 8.81.40.249 17.5.59.227
5.19.33.98 6.5.162.233 40.55.6.93 185.158.250.154
108.65.165.173 211.63.89.0 96.39.86.246 61.199.82.67