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

;; QUESTION SECTION:
;134.19.65.48.			IN	A

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

;; Query time: 13 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 22:17:15 CST 2025
;; MSG SIZE  rcvd: 105
Host info
Host 48.65.19.134.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 48.65.19.134.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
104.200.110.210 attackspam
2019-10-23T20:43:19.432820shield sshd\[22776\]: Invalid user 123456789a@ from 104.200.110.210 port 34798
2019-10-23T20:43:19.436970shield sshd\[22776\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.200.110.210
2019-10-23T20:43:21.158593shield sshd\[22776\]: Failed password for invalid user 123456789a@ from 104.200.110.210 port 34798 ssh2
2019-10-23T20:47:38.672653shield sshd\[23561\]: Invalid user pAsswORD from 104.200.110.210 port 44904
2019-10-23T20:47:38.680537shield sshd\[23561\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.200.110.210
2019-10-24 07:36:33
94.177.217.49 attackspam
Oct 24 00:49:17 jane sshd[4068]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.177.217.49 
Oct 24 00:49:18 jane sshd[4068]: Failed password for invalid user temp from 94.177.217.49 port 60916 ssh2
...
2019-10-24 07:34:09
45.136.111.109 attackbotsspam
Oct 23 22:10:37   TCP Attack: SRC=45.136.111.109 DST=[Masked] LEN=40 TOS=0x08 PREC=0x20 TTL=241  PROTO=TCP SPT=52093 DPT=12064 WINDOW=1024 RES=0x00 SYN URGP=0
2019-10-24 07:39:31
82.139.190.41 attack
xmlrpc attack
2019-10-24 07:15:42
58.199.164.240 attackbotsspam
2019-10-23T23:18:49.206395abusebot-5.cloudsearch.cf sshd\[11284\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=58.199.164.240  user=root
2019-10-24 07:25:55
119.29.245.158 attack
Oct 23 13:23:01 auw2 sshd\[25123\]: Invalid user print from 119.29.245.158
Oct 23 13:23:01 auw2 sshd\[25123\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.245.158
Oct 23 13:23:03 auw2 sshd\[25123\]: Failed password for invalid user print from 119.29.245.158 port 41128 ssh2
Oct 23 13:27:46 auw2 sshd\[25532\]: Invalid user qhsupport from 119.29.245.158
Oct 23 13:27:46 auw2 sshd\[25532\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.29.245.158
2019-10-24 07:43:33
76.27.163.60 attack
Invalid user jboss from 76.27.163.60 port 51328
2019-10-24 07:51:53
195.154.38.177 attack
5x Failed Password
2019-10-24 07:30:24
34.67.60.75 attack
2019-10-23T23:08:27.856514shield sshd\[13310\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=75.60.67.34.bc.googleusercontent.com  user=root
2019-10-23T23:08:29.058982shield sshd\[13310\]: Failed password for root from 34.67.60.75 port 36460 ssh2
2019-10-23T23:11:48.339626shield sshd\[13865\]: Invalid user cron from 34.67.60.75 port 46724
2019-10-23T23:11:48.344403shield sshd\[13865\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=75.60.67.34.bc.googleusercontent.com
2019-10-23T23:11:50.477222shield sshd\[13865\]: Failed password for invalid user cron from 34.67.60.75 port 46724 ssh2
2019-10-24 07:21:09
41.199.174.158 attackbotsspam
Port Scan: TCP/25
2019-10-24 07:41:30
123.131.135.246 attackspam
Oct 23 16:13:01 Tower sshd[40378]: Connection from 123.131.135.246 port 5349 on 192.168.10.220 port 22
Oct 23 16:13:03 Tower sshd[40378]: Invalid user ripley from 123.131.135.246 port 5349
Oct 23 16:13:03 Tower sshd[40378]: error: Could not get shadow information for NOUSER
Oct 23 16:13:03 Tower sshd[40378]: Failed password for invalid user ripley from 123.131.135.246 port 5349 ssh2
Oct 23 16:13:03 Tower sshd[40378]: Received disconnect from 123.131.135.246 port 5349:11: Bye Bye [preauth]
Oct 23 16:13:03 Tower sshd[40378]: Disconnected from invalid user ripley 123.131.135.246 port 5349 [preauth]
2019-10-24 07:17:17
54.36.150.26 attackspam
Automatic report - Banned IP Access
2019-10-24 07:43:11
213.230.96.243 attack
WordPress brute force
2019-10-24 07:20:46
124.217.235.145 attack
WordPress login Brute force / Web App Attack on client site.
2019-10-24 07:46:42
202.169.56.98 attackspambots
Invalid user smtpuser from 202.169.56.98 port 49053
2019-10-24 07:20:23

Recently Reported IPs

80.54.155.28 193.152.166.34 148.11.25.192 236.87.161.117
122.145.119.75 136.18.0.55 129.81.96.4 243.203.80.178
107.72.118.176 241.37.175.139 239.110.145.201 242.209.227.176
228.208.199.236 109.125.178.2 48.250.27.137 133.77.73.169
84.180.106.83 247.221.63.208 176.248.147.189 205.157.178.26