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

;; QUESTION SECTION:
;32.18.219.134.			IN	A

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

;; Query time: 92 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Jan 11 14:35:15 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 134.219.18.32.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 134.219.18.32.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
113.161.66.214 attack
SSH login attempts.
2020-03-29 12:35:28
156.207.176.235 attackbotsspam
SSH login attempts.
2020-03-29 13:03:11
45.77.79.163 attackspambots
SSH login attempts.
2020-03-29 12:32:06
91.121.175.138 attackbotsspam
Mar 29 05:51:23 ns382633 sshd\[19068\]: Invalid user sda from 91.121.175.138 port 45036
Mar 29 05:51:23 ns382633 sshd\[19068\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.175.138
Mar 29 05:51:25 ns382633 sshd\[19068\]: Failed password for invalid user sda from 91.121.175.138 port 45036 ssh2
Mar 29 05:59:28 ns382633 sshd\[20288\]: Invalid user pfw from 91.121.175.138 port 50838
Mar 29 05:59:28 ns382633 sshd\[20288\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=91.121.175.138
2020-03-29 12:47:32
132.232.8.58 attack
C1,WP GET /wp-login.php
2020-03-29 12:41:44
24.20.244.45 attackspambots
SSH login attempts.
2020-03-29 12:55:05
162.243.132.251 attackspambots
SSH login attempts.
2020-03-29 12:42:41
203.114.109.57 attackspambots
SSH login attempts.
2020-03-29 12:38:22
118.174.45.29 attack
SSH login attempts.
2020-03-29 12:43:00
93.94.180.4 attackbots
Mar 29 05:59:37 debian-2gb-nbg1-2 kernel: \[7713440.536399\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=93.94.180.4 DST=195.201.40.59 LEN=44 TOS=0x10 PREC=0x60 TTL=54 ID=8676 PROTO=TCP SPT=6500 DPT=23 WINDOW=31756 RES=0x00 SYN URGP=0
2020-03-29 12:35:57
118.24.212.156 attackbotsspam
SSH login attempts.
2020-03-29 12:41:59
60.248.52.1 attackspambots
SSH brute-force attempt
2020-03-29 12:49:39
110.228.236.108 attackspambots
Unauthorised access (Mar 29) SRC=110.228.236.108 LEN=40 TTL=49 ID=30441 TCP DPT=8080 WINDOW=52390 SYN
2020-03-29 13:07:56
45.148.10.91 attackbotsspam
45.148.10.91 was recorded 7 times by 7 hosts attempting to connect to the following ports: 123. Incident counter (4h, 24h, all-time): 7, 7, 56
2020-03-29 12:58:44
106.243.2.244 attackbots
SSH login attempts.
2020-03-29 12:42:15

Recently Reported IPs

120.110.249.141 207.37.107.170 72.130.232.3 98.112.165.87
199.25.67.39 24.233.115.66 0.14.220.107 93.83.255.51
166.112.138.211 212.229.44.253 128.54.211.47 122.180.252.141
175.121.136.151 236.24.125.83 158.63.253.204 35.100.119.177
54.0.249.10 120.32.145.175 228.33.29.117 198.27.117.0