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

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

;; QUESTION SECTION:
;104.18.43.195.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue May 24 01:44:38 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 195.43.18.104.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 195.43.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
62.65.78.89 attackbotsspam
Oct 31 17:57:39 debian64 sshd\[19390\]: Invalid user pi from 62.65.78.89 port 47480
Oct 31 17:57:40 debian64 sshd\[19389\]: Invalid user pi from 62.65.78.89 port 47478
Oct 31 17:57:40 debian64 sshd\[19390\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=62.65.78.89
...
2019-11-01 02:11:46
49.234.67.243 attack
Oct 31 10:08:28 debian sshd\[28725\]: Invalid user sdf432s from 49.234.67.243 port 60658
Oct 31 10:08:28 debian sshd\[28725\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.67.243
Oct 31 10:08:30 debian sshd\[28725\]: Failed password for invalid user sdf432s from 49.234.67.243 port 60658 ssh2
...
2019-11-01 02:14:07
221.132.113.188 attackspam
Unauthorized connection attempt from IP address 221.132.113.188 on Port 445(SMB)
2019-11-01 02:12:35
54.201.54.168 attackbots
Automatic report - Web App Attack
2019-11-01 02:07:10
139.59.13.223 attackspam
Oct 31 07:36:01 web1 sshd\[9405\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.13.223  user=root
Oct 31 07:36:03 web1 sshd\[9405\]: Failed password for root from 139.59.13.223 port 33152 ssh2
Oct 31 07:40:06 web1 sshd\[9799\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.13.223  user=root
Oct 31 07:40:08 web1 sshd\[9799\]: Failed password for root from 139.59.13.223 port 43550 ssh2
Oct 31 07:44:06 web1 sshd\[10149\]: Invalid user florence from 139.59.13.223
Oct 31 07:44:06 web1 sshd\[10149\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.13.223
2019-11-01 01:59:03
59.115.50.237 attackbotsspam
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/59.115.50.237/ 
 
 TW - 1H : (214)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : TW 
 NAME ASN : ASN3462 
 
 IP : 59.115.50.237 
 
 CIDR : 59.115.0.0/16 
 
 PREFIX COUNT : 390 
 
 UNIQUE IP COUNT : 12267520 
 
 
 ATTACKS DETECTED ASN3462 :  
  1H - 4 
  3H - 9 
  6H - 16 
 12H - 55 
 24H - 201 
 
 DateTime : 2019-10-31 13:00:41 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-11-01 02:13:50
171.224.181.252 attackbotsspam
Unauthorized connection attempt from IP address 171.224.181.252 on Port 445(SMB)
2019-11-01 02:08:45
211.230.194.99 attackspambots
firewall-block, port(s): 2323/tcp
2019-11-01 02:24:44
91.197.147.36 attack
Unauthorized connection attempt from IP address 91.197.147.36 on Port 445(SMB)
2019-11-01 01:55:54
171.223.203.106 attackbots
Unauthorized connection attempt from IP address 171.223.203.106 on Port 445(SMB)
2019-11-01 02:24:23
14.161.253.157 attackbotsspam
Unauthorized connection attempt from IP address 14.161.253.157 on Port 445(SMB)
2019-11-01 02:17:09
192.99.151.33 attackspam
$f2bV_matches
2019-11-01 02:28:06
18.237.179.197 attack
Oct 30 17:53:24 ihdb003 sshd[24508]: Connection from 18.237.179.197 port 48862 on 178.128.173.140 port 22
Oct 30 17:53:24 ihdb003 sshd[24508]: Did not receive identification string from 18.237.179.197 port 48862
Oct 30 17:53:59 ihdb003 sshd[24509]: Connection from 18.237.179.197 port 38336 on 178.128.173.140 port 22
Oct 30 17:54:00 ihdb003 sshd[24509]: User r.r from em3-18-237-179-197.us-west-2.compute.amazonaws.com not allowed because none of user's groups are listed in AllowGroups
Oct 30 17:54:00 ihdb003 sshd[24509]: Received disconnect from 18.237.179.197 port 38336:11: Normal Shutdown, Thank you for playing [preauth]
Oct 30 17:54:00 ihdb003 sshd[24509]: Disconnected from 18.237.179.197 port 38336 [preauth]
Oct 30 17:54:12 ihdb003 sshd[24513]: Connection from 18.237.179.197 port 42034 on 178.128.173.140 port 22
Oct 30 17:54:13 ihdb003 sshd[24513]: User r.r from em3-18-237-179-197.us-west-2.compute.amazonaws.com not allowed because none of user's groups are listed in ........
-------------------------------
2019-11-01 02:00:57
171.100.112.202 attackspambots
Unauthorized connection attempt from IP address 171.100.112.202 on Port 445(SMB)
2019-11-01 02:03:43
185.216.140.7 attackbots
ET DROP Dshield Block Listed Source group 1 - port: 3389 proto: TCP cat: Misc Attack
2019-11-01 02:26:03

Recently Reported IPs

104.18.42.31 104.18.43.197 104.18.43.219 104.18.43.26
104.18.43.29 104.18.43.30 104.18.43.32 104.18.43.38
104.18.43.40 104.18.43.48 104.18.43.55 104.18.43.63
104.18.43.65 104.18.43.68 104.18.43.78 104.18.43.85
104.192.80.218 104.193.108.87 104.193.111.139 104.193.111.250