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: Switzerland

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

;; QUESTION SECTION:
;194.132.61.61.			IN	A

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

;; Query time: 7 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Feb 19 22:31:20 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 61.61.132.194.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 194.132.61.61.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
185.173.35.17 attackspam
[portscan] tcp/81 [alter-web/web-proxy]
*(RWIN=65535)(04091111)
2020-04-09 17:08:17
37.187.125.32 attackbots
Apr  9 09:12:29 XXX sshd[65178]: Invalid user ftpuser2 from 37.187.125.32 port 59150
2020-04-09 16:52:32
140.143.245.30 attackspambots
'Fail2Ban'
2020-04-09 17:01:58
114.5.249.249 attackbotsspam
20/4/8@23:51:41: FAIL: Alarm-Network address from=114.5.249.249
...
2020-04-09 17:14:29
201.216.239.241 attackbots
Apr  9 11:41:39 hosting sshd[14488]: Invalid user bud from 201.216.239.241 port 51030
Apr  9 11:41:40 hosting sshd[14488]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.216.239.241
Apr  9 11:41:39 hosting sshd[14488]: Invalid user bud from 201.216.239.241 port 51030
Apr  9 11:41:42 hosting sshd[14488]: Failed password for invalid user bud from 201.216.239.241 port 51030 ssh2
...
2020-04-09 17:03:56
58.49.94.213 attackspam
$f2bV_matches
2020-04-09 17:06:00
71.6.232.5 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 60 - port: 25 proto: TCP cat: Misc Attack
2020-04-09 17:22:08
182.61.49.179 attack
Apr  9 10:24:44 xeon sshd[8132]: Failed password for invalid user deploy from 182.61.49.179 port 59168 ssh2
2020-04-09 17:10:08
180.164.51.146 attackbots
Apr  9 10:13:28 server sshd[10480]: Failed password for invalid user user from 180.164.51.146 port 42626 ssh2
Apr  9 10:26:59 server sshd[14436]: Failed password for invalid user maniruzzaman from 180.164.51.146 port 38706 ssh2
Apr  9 10:35:06 server sshd[16853]: Failed password for invalid user db1inst1 from 180.164.51.146 port 58788 ssh2
2020-04-09 16:59:12
104.244.77.95 attack
(mod_security) mod_security (id:210492) triggered by 104.244.77.95 (LU/Luxembourg/-): 5 in the last 3600 secs
2020-04-09 16:52:03
83.48.89.147 attackspambots
SSH brute-force: detected 8 distinct usernames within a 24-hour window.
2020-04-09 16:48:03
178.128.54.224 attackbots
AutoReport: Attempting to access '/wp-login.php?' (blacklisted keyword 'wp-')
2020-04-09 16:49:21
122.54.247.83 attack
Apr  9 14:58:58 f sshd\[29313\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.54.247.83
Apr  9 14:59:01 f sshd\[29313\]: Failed password for invalid user oracle from 122.54.247.83 port 56032 ssh2
Apr  9 15:09:28 f sshd\[29758\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.54.247.83
...
2020-04-09 17:03:33
151.80.144.255 attackbotsspam
SSH Brute-Force Attack
2020-04-09 16:40:19
179.184.59.109 attackspam
Apr  9 08:01:55 host5 sshd[10710]: Invalid user test from 179.184.59.109 port 42620
...
2020-04-09 16:44:28

Recently Reported IPs

103.208.104.238 121.169.175.5 5.133.192.199 185.12.151.99
159.65.148.196 27.46.75.11 147.185.133.26 135.225.84.187
81.17.103.232 176.236.102.232 44.204.228.85 85.239.235.152
185.76.57.123 147.185.133.53 64.176.34.33 14.212.61.235
111.20.134.120 111.0.0.76 39.154.6.203 36.161.112.167