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:
IP Type Details Datetime
45.134.26.49 attack
port scan
2021-07-28 06:50:03
45.134.26.227 attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 28 - port: 44269 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 21:00:22
45.134.26.222 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 27 - port: 44510 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 20:43:41
45.134.26.227 attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 28 - port: 44269 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 12:28:33
45.134.26.222 attackspam
ET CINS Active Threat Intelligence Poor Reputation IP group 27 - port: 44510 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 12:15:03
45.134.26.227 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 28 - port: 44269 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 05:18:17
45.134.26.222 attack
ET CINS Active Threat Intelligence Poor Reputation IP group 27 - port: 44510 proto: tcp cat: Misc Attackbytes: 60
2020-10-13 05:05:10
45.134.26.250 attack
Repeated RDP login failures. Last user: scanner
2020-10-05 04:02:49
45.134.26.250 attackspambots
Repeated RDP login failures. Last user: sqlservice
2020-10-04 19:53:38
45.134.26.250 attackbotsspam
Repeated RDP login failures. Last user: remote
2020-10-03 05:38:35
45.134.26.250 attackspam
Repeated RDP login failures. Last user: scanner
2020-10-03 01:03:01
45.134.26.250 attack
Repeated RDP login failures. Last user: scanner
2020-10-02 21:32:37
45.134.26.250 attackbotsspam
Repeated RDP login failures. Last user: front2
2020-10-02 18:05:20
45.134.26.250 attackbotsspam
Repeated RDP login failures. Last user: front2
2020-10-02 14:34:11
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 45.134.26.12
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30214
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;45.134.26.12.			IN	A

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

;; Query time: 19 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 14 08:45:49 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 12.26.134.45.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 12.26.134.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.220 attackbots
Oct 24 07:13:16 MK-Soft-Root1 sshd[5877]: Failed password for root from 222.186.175.220 port 25362 ssh2
Oct 24 07:13:26 MK-Soft-Root1 sshd[5877]: Failed password for root from 222.186.175.220 port 25362 ssh2
...
2019-10-24 13:15:16
119.30.114.213 attackbotsspam
" "
2019-10-24 13:07:24
202.152.38.75 attackbots
445/tcp 445/tcp 445/tcp...
[2019-09-12/10-24]14pkt,1pt.(tcp)
2019-10-24 12:47:48
209.90.178.190 attackbotsspam
Oct 24 05:39:22 km20725 sshd[5363]: reveeclipse mapping checking getaddrinfo for 209.90.178.190.gs.unused.primus.ca [209.90.178.190] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 24 05:39:22 km20725 sshd[5363]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.90.178.190  user=r.r
Oct 24 05:39:23 km20725 sshd[5363]: Failed password for r.r from 209.90.178.190 port 50846 ssh2
Oct 24 05:39:24 km20725 sshd[5363]: Received disconnect from 209.90.178.190: 11: Bye Bye [preauth]
Oct 24 05:51:39 km20725 sshd[6004]: reveeclipse mapping checking getaddrinfo for 209.90.178.190.gs.unused.primus.ca [209.90.178.190] failed - POSSIBLE BREAK-IN ATTEMPT!
Oct 24 05:51:39 km20725 sshd[6004]: Invalid user super from 209.90.178.190
Oct 24 05:51:39 km20725 sshd[6004]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=209.90.178.190
Oct 24 05:51:41 km20725 sshd[6004]: Failed password for invalid user super from 209.90.1........
-------------------------------
2019-10-24 12:58:16
212.83.132.246 attackspam
Automatic report - Banned IP Access
2019-10-24 12:41:26
159.39.246.39 attackspam
445/tcp 445/tcp 445/tcp...
[2019-10-13/24]6pkt,1pt.(tcp)
2019-10-24 12:55:42
142.93.201.168 attackspam
Oct 23 18:55:13 hanapaa sshd\[5308\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.201.168  user=root
Oct 23 18:55:15 hanapaa sshd\[5308\]: Failed password for root from 142.93.201.168 port 45185 ssh2
Oct 23 18:58:59 hanapaa sshd\[5636\]: Invalid user backupadmin from 142.93.201.168
Oct 23 18:58:59 hanapaa sshd\[5636\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=142.93.201.168
Oct 23 18:59:02 hanapaa sshd\[5636\]: Failed password for invalid user backupadmin from 142.93.201.168 port 36645 ssh2
2019-10-24 13:21:31
82.64.15.106 attackspambots
SSH invalid-user multiple login try
2019-10-24 12:54:46
115.165.127.21 attackbotsspam
23/tcp 23/tcp
[2019-09-05/10-24]2pkt
2019-10-24 12:54:17
185.220.101.5 attackbots
Oct 24 04:46:23 thevastnessof sshd[4364]: Failed password for root from 185.220.101.5 port 40101 ssh2
...
2019-10-24 13:01:51
188.166.87.238 attackspam
Too many connections or unauthorized access detected from Arctic banned ip
2019-10-24 13:03:58
104.214.234.214 attack
st-nyc1-01 recorded 3 login violations from 104.214.234.214 and was blocked at 2019-10-24 04:51:47. 104.214.234.214 has been blocked on 25 previous occasions. 104.214.234.214's first attempt was recorded at 2019-10-23 19:11:19
2019-10-24 12:59:54
49.36.14.120 attackbotsspam
49.36.14.120 - - \[23/Oct/2019:20:54:51 -0700\] "POST /index.php/admin/ HTTP/1.1" 404 2059949.36.14.120 - - \[23/Oct/2019:20:54:51 -0700\] "POST /index.php/admin HTTP/1.1" 404 2059549.36.14.120 - - \[23/Oct/2019:20:54:51 -0700\] "POST /index.php/admin/index/ HTTP/1.1" 404 20623
...
2019-10-24 13:01:25
182.253.222.203 attackspam
Oct 23 17:46:46 auw2 sshd\[16457\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.253.222.203  user=root
Oct 23 17:46:48 auw2 sshd\[16457\]: Failed password for root from 182.253.222.203 port 56092 ssh2
Oct 23 17:50:53 auw2 sshd\[16790\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.253.222.203  user=root
Oct 23 17:50:56 auw2 sshd\[16790\]: Failed password for root from 182.253.222.203 port 44432 ssh2
Oct 23 17:55:02 auw2 sshd\[17142\]: Invalid user kaushik from 182.253.222.203
2019-10-24 12:51:31
41.217.216.39 attackbots
2019-10-24T04:33:19.523016shield sshd\[16343\]: Invalid user slurm from 41.217.216.39 port 47362
2019-10-24T04:33:19.530787shield sshd\[16343\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.217.216.39
2019-10-24T04:33:20.953108shield sshd\[16343\]: Failed password for invalid user slurm from 41.217.216.39 port 47362 ssh2
2019-10-24T04:38:42.017364shield sshd\[17893\]: Invalid user munin from 41.217.216.39 port 57406
2019-10-24T04:38:42.021336shield sshd\[17893\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=41.217.216.39
2019-10-24 12:49:38

Recently Reported IPs

45.134.26.10 45.134.26.11 45.134.26.126 45.134.26.15
45.134.26.13 45.134.26.17 45.134.26.19 45.134.26.16
45.134.26.21 45.134.26.25 45.134.26.27 45.134.26.20
45.134.26.28 45.134.26.29 45.136.161.2 45.136.14.134
45.136.162.2 45.136.160.2 45.136.31.61 45.136.52.5