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 of America (the)

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

;; QUESTION SECTION:
;136.34.20.19.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 07 08:47:00 CST 2025
;; MSG SIZE  rcvd: 105
Host info
19.20.34.136.in-addr.arpa domain name pointer 136-34-20-19.googlefiber.net.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
19.20.34.136.in-addr.arpa	name = 136-34-20-19.googlefiber.net.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
101.108.131.189 attackbots
Automatic report - Port Scan Attack
2019-10-04 04:33:50
51.254.95.139 attackspam
2019-10-03 16:10:34,975 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 16:44:20,818 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 17:15:55,565 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 17:46:44,063 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
2019-10-03 18:21:03,279 fail2ban.actions        \[946\]: NOTICE  \[sshd\] Ban 51.254.95.139
...
2019-10-04 04:28:08
92.118.160.45 attackspambots
Automatic report - Port Scan Attack
2019-10-04 04:39:25
95.154.203.137 attackbotsspam
Oct  3 11:22:49 ws19vmsma01 sshd[234333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=95.154.203.137
Oct  3 11:22:51 ws19vmsma01 sshd[234333]: Failed password for invalid user git from 95.154.203.137 port 39024 ssh2
...
2019-10-04 04:03:07
122.116.174.239 attackbots
Oct  3 19:34:19 hcbbdb sshd\[11644\]: Invalid user mcserv from 122.116.174.239
Oct  3 19:34:19 hcbbdb sshd\[11644\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122-116-174-239.hinet-ip.hinet.net
Oct  3 19:34:21 hcbbdb sshd\[11644\]: Failed password for invalid user mcserv from 122.116.174.239 port 46500 ssh2
Oct  3 19:36:46 hcbbdb sshd\[11927\]: Invalid user webmaster from 122.116.174.239
Oct  3 19:36:46 hcbbdb sshd\[11927\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122-116-174-239.hinet-ip.hinet.net
2019-10-04 04:02:21
51.77.193.28 attack
WordPress wp-login brute force :: 51.77.193.28 0.132 BYPASS [04/Oct/2019:06:08:05  1000] [censored_1] "POST /wp-login.php HTTP/1.1" 200 3972 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
2019-10-04 04:27:25
51.15.191.156 attackbots
RDP brute force attack detected by fail2ban
2019-10-04 04:02:37
200.44.50.155 attackspambots
Oct  3 07:59:20 web9 sshd\[30676\]: Invalid user network2 from 200.44.50.155
Oct  3 07:59:20 web9 sshd\[30676\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.44.50.155
Oct  3 07:59:21 web9 sshd\[30676\]: Failed password for invalid user network2 from 200.44.50.155 port 43364 ssh2
Oct  3 08:04:18 web9 sshd\[31415\]: Invalid user db2inst from 200.44.50.155
Oct  3 08:04:18 web9 sshd\[31415\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.44.50.155
2019-10-04 04:17:51
193.70.42.33 attackspambots
Oct  3 22:17:47 SilenceServices sshd[12166]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.42.33
Oct  3 22:17:48 SilenceServices sshd[12166]: Failed password for invalid user webuser from 193.70.42.33 port 38318 ssh2
Oct  3 22:21:53 SilenceServices sshd[13304]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.42.33
2019-10-04 04:35:40
185.234.219.83 attack
Oct  3 23:09:45 elektron postfix/smtpd\[32109\]: warning: unknown\[185.234.219.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  3 23:23:29 elektron postfix/smtpd\[2062\]: warning: unknown\[185.234.219.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Oct  3 23:37:06 elektron postfix/smtpd\[964\]: warning: unknown\[185.234.219.83\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
2019-10-04 04:41:44
193.253.97.116 attackbotsspam
Oct  3 20:53:05 bouncer sshd\[18027\]: Invalid user P4SS123 from 193.253.97.116 port 2822
Oct  3 20:53:05 bouncer sshd\[18027\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.253.97.116 
Oct  3 20:53:07 bouncer sshd\[18027\]: Failed password for invalid user P4SS123 from 193.253.97.116 port 2822 ssh2
...
2019-10-04 04:12:37
219.146.157.242 attackspambots
Attempt to attack host OS, exploiting network vulnerabilities, on 03-10-2019 13:20:30.
2019-10-04 04:38:29
89.248.174.214 attackspambots
10/03/2019-15:23:32.080673 89.248.174.214 Protocol: 6 ET CINS Active Threat Intelligence Poor Reputation IP group 98
2019-10-04 04:34:20
92.118.160.53 attackspam
03.10.2019 20:09:25 Connection to port 1521 blocked by firewall
2019-10-04 04:26:39
92.118.160.9 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-04 04:16:03

Recently Reported IPs

97.5.181.133 188.131.80.128 238.27.228.4 71.161.75.94
13.97.141.244 69.75.5.15 22.112.254.233 218.216.196.101
59.211.45.143 131.51.187.42 67.21.105.45 40.240.54.49
144.71.170.61 2.112.67.146 188.132.234.118 131.169.218.70
252.72.26.66 223.82.221.80 134.144.130.77 61.207.220.222