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

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

;; QUESTION SECTION:
;141.45.126.53.			IN	A

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

;; Query time: 71 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Jun 08 13:51:14 CST 2022
;; MSG SIZE  rcvd: 106
Host info
53.126.45.141.in-addr.arpa domain name pointer hip2.vb.htw-berlin.de.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
53.126.45.141.in-addr.arpa	name = hip2.vb.htw-berlin.de.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
177.220.252.45 attack
SSH Bruteforce Attack
2019-07-29 22:45:41
92.119.160.250 attackspambots
29.07.2019 12:51:10 Connection to port 4442 blocked by firewall
2019-07-29 22:05:23
140.143.67.146 attackspam
Jul 29 02:22:45 hostnameproxy sshd[7909]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.67.146  user=r.r
Jul 29 02:22:47 hostnameproxy sshd[7909]: Failed password for r.r from 140.143.67.146 port 53666 ssh2
Jul 29 02:25:57 hostnameproxy sshd[7952]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.67.146  user=r.r
Jul 29 02:25:59 hostnameproxy sshd[7952]: Failed password for r.r from 140.143.67.146 port 56804 ssh2
Jul 29 02:27:21 hostnameproxy sshd[7965]: Invalid user 1234 from 140.143.67.146 port 43642
Jul 29 02:27:21 hostnameproxy sshd[7965]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=140.143.67.146
Jul 29 02:27:22 hostnameproxy sshd[7965]: Failed password for invalid user 1234 from 140.143.67.146 port 43642 ssh2
Jul 29 02:28:39 hostnameproxy sshd[7983]: Invalid user test123+ from 140.143.67.146 port 58680
Jul 29 02:28:39 hostname........
------------------------------
2019-07-29 22:49:23
46.236.117.186 attackbotsspam
Trying to (more than 3 packets) bruteforce (not open) telnet port 23
2019-07-29 22:38:10
59.36.132.222 attackbotsspam
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-07-29 22:19:09
124.89.2.202 attackbots
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-07-29 22:00:47
91.206.15.33 attack
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-07-29 22:10:28
218.201.83.148 attackbotsspam
failed_logins
2019-07-29 22:41:29
125.64.94.212 attackspam
Port scan attempt detected by AWS-CCS, CTS, India
2019-07-29 21:59:41
133.130.97.118 attackbots
SSH/22 MH Probe, BF, Hack -
2019-07-29 22:48:42
66.240.192.39 attackspam
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-07-29 22:18:50
92.53.65.189 attack
firewall-block, port(s): 3697/tcp, 3815/tcp
2019-07-29 22:07:32
120.52.152.15 attack
29.07.2019 12:18:00 Connection to port 67 blocked by firewall
2019-07-29 22:03:39
184.105.139.114 attack
Scanning (more than 2 packets) random ports - tries to find possible vulnerable services
2019-07-29 21:52:48
46.21.146.110 attackspam
firewall-block, port(s): 11211/tcp
2019-07-29 22:20:35

Recently Reported IPs

59.140.129.41 253.40.83.178 234.124.113.31 151.71.240.39
82.52.210.225 68.63.166.137 189.213.77.69 203.4.129.165
46.149.19.172 204.72.142.230 194.56.234.102 123.8.231.204
4.115.223.2 202.91.168.175 170.102.122.188 136.179.13.173
193.134.64.232 229.154.117.147 253.192.102.218 65.94.144.255