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

;; QUESTION SECTION:
;104.19.134.80.			IN	A

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

;; Query time: 65 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 18 01:56:57 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 80.134.19.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 80.134.19.104.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
42.159.83.169 attackbots
Mar  4 06:02:11 targaryen sshd[20020]: Invalid user eupa from 42.159.83.169
Mar  4 06:08:37 targaryen sshd[20062]: Invalid user eupa from 42.159.83.169
Mar  4 06:15:02 targaryen sshd[20226]: Invalid user ubuntu from 42.159.83.169
Mar  4 06:21:32 targaryen sshd[20269]: Invalid user www from 42.159.83.169
...
2020-03-04 21:14:23
92.63.194.59 attackbotsspam
$f2bV_matches | Triggered by Fail2Ban at Vostok web server
2020-03-04 20:36:49
122.51.62.212 attack
(sshd) Failed SSH login from 122.51.62.212 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Mar  4 11:42:04 amsweb01 sshd[22193]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.51.62.212  user=root
Mar  4 11:42:06 amsweb01 sshd[22193]: Failed password for root from 122.51.62.212 port 50654 ssh2
Mar  4 11:59:17 amsweb01 sshd[24432]: Invalid user tmp from 122.51.62.212 port 33108
Mar  4 11:59:19 amsweb01 sshd[24432]: Failed password for invalid user tmp from 122.51.62.212 port 33108 ssh2
Mar  4 12:03:45 amsweb01 sshd[25086]: User bin from 122.51.62.212 not allowed because not listed in AllowUsers
2020-03-04 21:06:12
37.151.121.139 attack
Email rejected due to spam filtering
2020-03-04 20:40:51
171.242.87.71 attack
Brute force attempt
2020-03-04 20:41:10
155.94.143.226 attackbotsspam
Port 6380 scan denied
2020-03-04 21:09:41
159.65.152.201 attackspambots
Mar  3 19:58:58 server sshd\[5247\]: Invalid user trade from 159.65.152.201
Mar  3 19:58:58 server sshd\[5247\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.152.201 
Mar  3 19:59:00 server sshd\[5247\]: Failed password for invalid user trade from 159.65.152.201 port 43322 ssh2
Mar  4 14:54:44 server sshd\[8668\]: Invalid user rtest from 159.65.152.201
Mar  4 14:54:44 server sshd\[8668\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.152.201 
...
2020-03-04 20:52:11
162.238.213.216 attack
$f2bV_matches
2020-03-04 20:59:00
112.215.113.11 attackspambots
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.215.113.11  user=uucp
Failed password for uucp from 112.215.113.11 port 46565 ssh2
Invalid user mailman from 112.215.113.11 port 42645
pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.215.113.11
Failed password for invalid user mailman from 112.215.113.11 port 42645 ssh2
2020-03-04 20:53:11
222.186.175.181 attackbots
Mar  4 13:43:58 eventyay sshd[30375]: Failed password for root from 222.186.175.181 port 15620 ssh2
Mar  4 13:44:12 eventyay sshd[30375]: error: maximum authentication attempts exceeded for root from 222.186.175.181 port 15620 ssh2 [preauth]
Mar  4 13:44:18 eventyay sshd[30378]: Failed password for root from 222.186.175.181 port 48682 ssh2
...
2020-03-04 20:46:17
69.229.6.47 attack
Mar  4 07:11:23 lnxded64 sshd[13681]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=69.229.6.47
2020-03-04 20:37:57
144.217.214.13 attack
Mar  3 21:16:15 web1 sshd\[13443\]: Invalid user gameserver from 144.217.214.13
Mar  3 21:16:15 web1 sshd\[13443\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.214.13
Mar  3 21:16:17 web1 sshd\[13443\]: Failed password for invalid user gameserver from 144.217.214.13 port 37376 ssh2
Mar  3 21:21:52 web1 sshd\[13915\]: Invalid user testuser from 144.217.214.13
Mar  3 21:21:52 web1 sshd\[13915\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=144.217.214.13
2020-03-04 20:52:51
185.143.223.160 attackspam
Receiving 1000's of email every day for months. Appear to be using a word list to create email addresses (random word)@mydomain...  Also using random characters in the senders name using correct domain names: 2dzd5ioyjod2b@lulucoffee.co.uk, s5yx0sbnjiumvp6@galatasaray.com, 2v5a9qyn3oqktv6@central-marketer.com

Event:	rejected rejected
User:	-remote-
Domain:	
From Address:	s5yx0sbnjiumvp6@galatasaray.com
Sender:	
Sent Time:	Mar 4, 2020, 6:02:06 AM
Sender Host:	185.143.223.160
Sender IP:	185.143.223.160
Authentication:	unauthorized
Spam Score:	0
Recipient:	delusional@MYDOMAIN
Delivered To:	
Router:	reject
Transport:	**rejected**
Out Time:	Mar 4, 2020, 6:02:06 AM
ID:	1j9N6e-0008Qm-mF
Delivery Host:	185.143.223.160
Delivery IP:	185.143.223.160
Size:	0 bytes
Result:	No Such User Here
2020-03-04 21:05:29
23.111.178.11 attack
Mar  4 06:54:08 server sshd[2562239]: Failed password for invalid user arai from 23.111.178.11 port 40450 ssh2
Mar  4 07:03:21 server sshd[2576728]: Failed password for invalid user artif from 23.111.178.11 port 60440 ssh2
Mar  4 07:12:53 server sshd[2591920]: Failed password for invalid user carlo from 23.111.178.11 port 55786 ssh2
2020-03-04 20:56:18
123.19.66.104 attack
Email rejected due to spam filtering
2020-03-04 20:58:40

Recently Reported IPs

104.19.135.102 104.19.135.75 104.19.136.100 104.19.136.90
104.19.134.75 104.19.136.75 104.19.137.100 104.19.138.104
104.19.137.75 104.19.138.75 104.19.137.90 104.21.65.97
104.19.139.104 104.19.139.75 104.19.139.77 104.19.138.77
104.19.141.75 104.19.141.77 104.19.140.75 104.19.140.77