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

;; QUESTION SECTION:
;45.134.26.122.			IN	A

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

;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 17:34:35 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 122.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 122.26.134.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
49.51.9.134 attackspam
Unauthorized connection attempt detected from IP address 49.51.9.134 to port 22
2020-07-01 18:56:17
80.82.77.33 attackbotsspam
" "
2020-07-01 19:01:13
185.234.216.28 attackspam
2020/06/30 20:04:37 [error] 170985#0: *205 open() "/local/nginx/wp-login.php" failed (2: No such file or directory), client: 185.234.216.28, server: _, request: "GET /wp-login.php HTTP/1.1", host: "micled.net"
2020/06/30 20:04:37 [error] 170985#0: *205 open() "/local/nginx/wp-login.php" failed (2: No such file or directory), client: 185.234.216.28, server: _, request: "GET //wp-login.php HTTP/1.1", host: "micled.net"
2020-07-01 19:07:32
128.199.130.217 attackspam
detected by Fail2Ban
2020-07-01 18:24:53
190.182.47.194 attack
Unauthorized connection attempt detected from IP address 190.182.47.194 to port 23
2020-07-01 18:55:10
51.91.56.33 attackspam
Jun 30 20:10:27 jane sshd[11596]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.91.56.33 
Jun 30 20:10:29 jane sshd[11596]: Failed password for invalid user angel from 51.91.56.33 port 53918 ssh2
...
2020-07-01 18:44:03
71.6.233.141 attackspambots
firewall-block, port(s): 8081/tcp
2020-07-01 19:01:46
14.161.38.227 attackbots
Unauthorized connection attempt from IP address 14.161.38.227 on Port 445(SMB)
2020-07-01 19:02:58
159.89.200.32 attackspam
2020-06-29T21:50:33.644080abusebot-3.cloudsearch.cf sshd[31467]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=blogunik.com  user=root
2020-06-29T21:50:35.966871abusebot-3.cloudsearch.cf sshd[31467]: Failed password for root from 159.89.200.32 port 39672 ssh2
2020-06-29T21:52:29.624627abusebot-3.cloudsearch.cf sshd[31475]: Invalid user admin from 159.89.200.32 port 48592
2020-06-29T21:52:29.630334abusebot-3.cloudsearch.cf sshd[31475]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=blogunik.com
2020-06-29T21:52:29.624627abusebot-3.cloudsearch.cf sshd[31475]: Invalid user admin from 159.89.200.32 port 48592
2020-06-29T21:52:31.210558abusebot-3.cloudsearch.cf sshd[31475]: Failed password for invalid user admin from 159.89.200.32 port 48592 ssh2
2020-06-29T21:54:28.118306abusebot-3.cloudsearch.cf sshd[31479]: Invalid user \n from 159.89.200.32 port 57548
...
2020-07-01 18:41:37
221.223.35.118 attackbotsspam
Telnet Server BruteForce Attack
2020-07-01 18:36:53
71.6.233.34 attackbots
unauthorized connection attempt
2020-07-01 18:59:07
178.79.172.217 attackspam
 UDP 178.79.172.217:40388 -> port 1434, len 29
2020-07-01 18:55:39
110.78.114.236 attackbots
leo_www
2020-07-01 18:58:11
111.165.101.10 attackspam
Port Scan detected!
...
2020-07-01 18:33:20
114.34.50.84 attackspam
Honeypot attack, port: 81, PTR: 114-34-50-84.HINET-IP.hinet.net.
2020-07-01 18:57:48

Recently Reported IPs

45.134.26.115 45.134.26.125 45.136.53.18 45.137.13.115
45.134.26.73 45.137.13.135 45.137.13.173 45.137.13.246
45.137.13.253 45.137.13.46 45.137.13.184 45.137.13.83
45.137.155.30 45.138.102.105 45.138.101.170 45.138.103.117
45.138.102.128 45.138.102.135 45.137.22.112 45.138.101.102