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

;; QUESTION SECTION:
;45.134.26.72.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Feb 07 15:02:32 CST 2022
;; MSG SIZE  rcvd: 105
Host info
Host 72.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 72.26.134.45.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
212.129.154.148 attackspambots
364. On May 17 2020 experienced a Brute Force SSH login attempt -> 1 unique times by 212.129.154.148.
2020-05-20 23:26:00
218.92.0.212 attackspambots
May 20 16:33:45 * sshd[30981]: Failed password for root from 218.92.0.212 port 28829 ssh2
May 20 16:34:01 * sshd[30981]: error: maximum authentication attempts exceeded for root from 218.92.0.212 port 28829 ssh2 [preauth]
2020-05-20 22:48:11
51.91.39.84 attackbots
$f2bV_matches
2020-05-20 23:17:19
188.49.157.23 attack
Attempted connection to port 445.
2020-05-20 23:18:28
113.190.242.194 attackspam
Unauthorized connection attempt from IP address 113.190.242.194 on Port 445(SMB)
2020-05-20 22:59:35
197.50.45.114 attack
Unauthorized connection attempt from IP address 197.50.45.114 on Port 445(SMB)
2020-05-20 22:53:41
13.232.84.22 attackspambots
Attempted connection to port 21607.
2020-05-20 23:25:28
161.35.61.27 attackbots
May 20 16:35:51 home sshd[21679]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.35.61.27
May 20 16:35:53 home sshd[21679]: Failed password for invalid user gqc from 161.35.61.27 port 47126 ssh2
May 20 16:39:54 home sshd[22731]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=161.35.61.27
...
2020-05-20 22:46:28
218.92.0.138 attackbots
2020-05-20T14:34:23.611113shield sshd\[22264\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.138  user=root
2020-05-20T14:34:25.304610shield sshd\[22264\]: Failed password for root from 218.92.0.138 port 40098 ssh2
2020-05-20T14:34:28.006893shield sshd\[22264\]: Failed password for root from 218.92.0.138 port 40098 ssh2
2020-05-20T14:34:31.779231shield sshd\[22264\]: Failed password for root from 218.92.0.138 port 40098 ssh2
2020-05-20T14:34:35.265890shield sshd\[22264\]: Failed password for root from 218.92.0.138 port 40098 ssh2
2020-05-20 22:57:29
113.188.149.43 attackbots
Attempted connection to port 445.
2020-05-20 23:31:17
222.186.30.112 attack
May 20 16:49:13 dev0-dcde-rnet sshd[15578]: Failed password for root from 222.186.30.112 port 12620 ssh2
May 20 16:49:22 dev0-dcde-rnet sshd[15580]: Failed password for root from 222.186.30.112 port 52201 ssh2
2020-05-20 22:52:35
79.101.96.74 attack
Has been ddosing our servers
2020-05-20 23:09:46
77.49.120.106 attackspambots
Attempted connection to port 23.
2020-05-20 23:03:01
217.61.7.72 attack
May 20 10:28:12 pve1 sshd[848]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=217.61.7.72 
May 20 10:28:13 pve1 sshd[848]: Failed password for invalid user ijf from 217.61.7.72 port 58970 ssh2
...
2020-05-20 23:18:08
200.236.96.89 attackbots
Automatic report - Port Scan Attack
2020-05-20 22:58:02

Recently Reported IPs

203.127.39.7 220.132.211.1 202.4.126.113 113.104.245.210
176.31.95.232 222.181.11.168 164.90.199.9 51.211.183.190
218.24.198.161 188.32.72.56 157.230.97.232 143.202.95.44
171.228.170.63 93.151.254.167 141.98.81.139 138.118.235.162
177.72.78.202 175.101.81.251 221.118.59.80 41.77.173.106