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: Frankfurt am Main

Region: Hessen

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

;; QUESTION SECTION:
;18.195.43.99.			IN	A

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

;; Query time: 11 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 03 02:32:16 CST 2025
;; MSG SIZE  rcvd: 105
Host info
99.43.195.18.in-addr.arpa domain name pointer ec2-18-195-43-99.eu-central-1.compute.amazonaws.com.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
99.43.195.18.in-addr.arpa	name = ec2-18-195-43-99.eu-central-1.compute.amazonaws.com.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
176.97.48.233 attack
" "
2019-11-17 08:06:51
177.106.159.85 attackbotsspam
Telnet/23 MH Probe, BF, Hack -
2019-11-17 08:01:31
188.131.173.220 attackbots
Nov 17 00:11:37 srv01 sshd[26509]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.173.220  user=sync
Nov 17 00:11:39 srv01 sshd[26509]: Failed password for sync from 188.131.173.220 port 45650 ssh2
Nov 17 00:16:06 srv01 sshd[26750]: Invalid user binod from 188.131.173.220
Nov 17 00:16:06 srv01 sshd[26750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=188.131.173.220
Nov 17 00:16:06 srv01 sshd[26750]: Invalid user binod from 188.131.173.220
Nov 17 00:16:08 srv01 sshd[26750]: Failed password for invalid user binod from 188.131.173.220 port 34216 ssh2
...
2019-11-17 07:58:08
221.224.239.238 attackspam
DATE:2019-11-16 23:58:06, IP:221.224.239.238, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2019-11-17 08:09:38
110.173.50.50 attackspambots
Nov 17 00:54:21 www4 sshd\[62950\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=110.173.50.50  user=root
Nov 17 00:54:24 www4 sshd\[62950\]: Failed password for root from 110.173.50.50 port 42812 ssh2
Nov 17 00:58:05 www4 sshd\[63396\]: Invalid user Martta from 110.173.50.50
...
2019-11-17 08:10:12
45.80.65.82 attackspam
Nov 17 00:32:43 eventyay sshd[13569]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.65.82
Nov 17 00:32:45 eventyay sshd[13569]: Failed password for invalid user centra from 45.80.65.82 port 50048 ssh2
Nov 17 00:39:53 eventyay sshd[13631]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=45.80.65.82
...
2019-11-17 07:41:55
45.82.153.76 attack
2019-11-16 00:57:16 server smtpd[39009]: warning: unknown[45.82.153.76]:38716: SASL CRAM-MD5 authentication failed: PDY5NTI4NjQwMzU1NjU4NDIuMTU3Mzg5NDYzMUBzY2FsbG9wLmxvY2FsPg==
2019-11-17 07:45:34
185.156.177.235 attackspambots
Connection by 185.156.177.235 on port: 195 got caught by honeypot at 11/16/2019 10:35:23 PM
2019-11-17 07:42:22
114.244.235.8 attackspambots
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/114.244.235.8/ 
 
 CN - 1H : (678)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4808 
 
 IP : 114.244.235.8 
 
 CIDR : 114.244.192.0/18 
 
 PREFIX COUNT : 1972 
 
 UNIQUE IP COUNT : 6728192 
 
 
 ATTACKS DETECTED ASN4808 :  
  1H - 4 
  3H - 7 
  6H - 15 
 12H - 22 
 24H - 36 
 
 DateTime : 2019-11-16 23:58:14 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-17 08:04:17
45.227.255.75 attackspambots
Trying ports that it shouldn't be.
2019-11-17 08:17:22
66.249.69.79 attackbotsspam
Calling not existent HTTP content (400 or 404).
2019-11-17 07:33:54
49.235.214.68 attackbotsspam
2019-11-16T23:45:21.362635shield sshd\[14668\]: Invalid user jahari from 49.235.214.68 port 50224
2019-11-16T23:45:21.367060shield sshd\[14668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.214.68
2019-11-16T23:45:23.320116shield sshd\[14668\]: Failed password for invalid user jahari from 49.235.214.68 port 50224 ssh2
2019-11-16T23:49:56.369273shield sshd\[15805\]: Invalid user grohler from 49.235.214.68 port 56504
2019-11-16T23:49:56.372326shield sshd\[15805\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.214.68
2019-11-17 07:57:25
134.236.43.245 attackspambots
port 23 attempt blocked
2019-11-17 08:03:03
180.244.90.110 attackbotsspam
Telnetd brute force attack detected by fail2ban
2019-11-17 07:33:23
222.186.180.147 attack
F2B jail: sshd. Time: 2019-11-17 01:13:05, Reported by: VKReport
2019-11-17 08:14:39

Recently Reported IPs

18.224.73.166 18.169.134.0 18.158.61.235 18.144.83.146
18.134.9.220 18.133.73.248 18.132.45.50 18.130.50.209
18.117.187.150 176.34.165.218 16.52.34.43 16.171.110.52
15.229.4.110 15.223.189.101 15.168.61.123 15.168.137.38
15.152.52.80 13.57.213.120 13.50.224.198 13.41.69.35