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: United States

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

;; QUESTION SECTION:
;104.18.194.35.			IN	A

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

;; Query time: 116 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 03:24:34 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 35.194.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 35.194.18.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
139.59.183.112 attack
Sep 26 20:14:25 markkoudstaal sshd[1622]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.183.112
Sep 26 20:14:27 markkoudstaal sshd[1622]: Failed password for invalid user user from 139.59.183.112 port 46979 ssh2
Sep 26 20:18:30 markkoudstaal sshd[2032]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.59.183.112
2019-09-27 02:49:55
222.87.0.79 attackspam
2019-09-26T05:33:52.562755suse-nuc sshd[23033]: Invalid user test from 222.87.0.79 port 43947
...
2019-09-27 03:09:46
222.72.39.138 attackspambots
Unauthorized connection attempt from IP address 222.72.39.138 on Port 445(SMB)
2019-09-27 02:57:00
90.188.16.246 attack
postfix (unknown user, SPF fail or relay access denied)
2019-09-27 02:51:29
128.199.142.138 attackbotsspam
Sep 26 08:31:07 tdfoods sshd\[28746\]: Invalid user 654321 from 128.199.142.138
Sep 26 08:31:07 tdfoods sshd\[28746\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138
Sep 26 08:31:09 tdfoods sshd\[28746\]: Failed password for invalid user 654321 from 128.199.142.138 port 45744 ssh2
Sep 26 08:35:44 tdfoods sshd\[29128\]: Invalid user omn from 128.199.142.138
Sep 26 08:35:44 tdfoods sshd\[29128\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.142.138
2019-09-27 02:39:47
41.78.201.48 attackbotsspam
SSH Brute Force, server-1 sshd[30242]: Failed password for root from 41.78.201.48 port 54224 ssh2
2019-09-27 02:33:55
182.71.45.254 attackspambots
Unauthorized connection attempt from IP address 182.71.45.254 on Port 445(SMB)
2019-09-27 02:48:19
89.36.220.145 attack
Sep 26 12:28:10 TORMINT sshd\[16197\]: Invalid user resumes from 89.36.220.145
Sep 26 12:28:10 TORMINT sshd\[16197\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.36.220.145
Sep 26 12:28:13 TORMINT sshd\[16197\]: Failed password for invalid user resumes from 89.36.220.145 port 33850 ssh2
...
2019-09-27 02:58:05
41.237.23.48 attack
Honeypot attack, port: 23, PTR: host-41.237.23.48.tedata.net.
2019-09-27 03:01:36
125.129.92.96 attackspam
Sep 26 14:34:27 lnxded64 sshd[5845]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=125.129.92.96
2019-09-27 02:36:37
92.148.63.132 attack
Sep 26 16:38:48 bouncer sshd\[12868\]: Invalid user test from 92.148.63.132 port 37518
Sep 26 16:38:48 bouncer sshd\[12868\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=92.148.63.132 
Sep 26 16:38:50 bouncer sshd\[12868\]: Failed password for invalid user test from 92.148.63.132 port 37518 ssh2
...
2019-09-27 02:45:59
77.247.110.201 attack
\[2019-09-26 14:30:39\] NOTICE\[1948\] chan_sip.c: Registration from '\' failed for '77.247.110.201:63737' - Wrong password
\[2019-09-26 14:30:39\] SECURITY\[2006\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-09-26T14:30:39.987-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="1567",SessionID="0x7f1e1c11c748",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247.110.201/63737",Challenge="6ed70ac8",ReceivedChallenge="6ed70ac8",ReceivedHash="fbeea1afacec04e39bc1081d681c2797"
\[2019-09-26 14:31:18\] NOTICE\[1948\] chan_sip.c: Registration from '\' failed for '77.247.110.201:50440' - Wrong password
\[2019-09-26 14:31:18\] SECURITY\[2006\] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2019-09-26T14:31:18.134-0400",Severity="Error",Service="SIP",EventVersion="2",AccountID="606",SessionID="0x7f1e1c11c748",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/77.247.110.201/50440",Ch
2019-09-27 02:47:20
176.31.100.19 attackbotsspam
$f2bV_matches
2019-09-27 02:57:33
5.255.250.113 attackbots
Yandexbots blocked  IP: 5.255.250.113 Hostname: 5-255-250-113.spider.yandex.com
Human/Bot: Bot
Browser: undefined
Mozilla/5.0 (compatible; YandexBot/3.0; +http://yandex.com/bots)
2019-09-27 03:08:23
189.204.6.115 attack
Unauthorized connection attempt from IP address 189.204.6.115 on Port 445(SMB)
2019-09-27 03:06:59

Recently Reported IPs

104.18.194.31 104.18.195.31 104.18.195.35 104.18.195.94
104.18.196.46 104.18.196.94 104.18.197.46 104.18.198.35
112.198.114.245 104.18.198.74 104.18.199.235 104.18.199.35
104.18.199.74 104.18.2.120 104.18.2.144 104.18.2.179
104.18.2.184 104.18.2.202 104.18.2.214 104.18.2.227