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

Region: Land Berlin

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;141.20.105.14.			IN	A

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

;; Query time: 64 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Sep 05 09:08:57 CST 2020
;; MSG SIZE  rcvd: 117
Host info
Host 14.105.20.141.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 14.105.20.141.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
134.175.219.96 attackspam
Triggered by Fail2Ban at Vostok web server
2019-12-09 06:39:24
118.98.27.222 attackspambots
Unauthorized connection attempt detected from IP address 118.98.27.222 to port 445
2019-12-09 06:18:38
92.246.85.165 attackbotsspam
" "
2019-12-09 06:48:48
198.108.66.30 attackbotsspam
firewall-block, port(s): 8888/tcp
2019-12-09 06:32:45
139.162.104.208 attack
21/tcp 21/tcp 21/tcp...
[2019-10-22/12-07]50pkt,1pt.(tcp)
2019-12-09 06:16:20
125.64.94.211 attackspambots
Multiport scan : 6 ports scanned 5984(x2) 6379 9200 11211 27017(x3) 28017
2019-12-09 06:19:23
193.70.33.75 attackbotsspam
Dec  8 15:50:20 icinga sshd[10736]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.33.75
Dec  8 15:50:22 icinga sshd[10736]: Failed password for invalid user cecilia from 193.70.33.75 port 40800 ssh2
...
2019-12-09 06:17:53
201.140.111.58 attackbotsspam
Dec  8 17:39:01 TORMINT sshd\[16454\]: Invalid user apache from 201.140.111.58
Dec  8 17:39:01 TORMINT sshd\[16454\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=201.140.111.58
Dec  8 17:39:04 TORMINT sshd\[16454\]: Failed password for invalid user apache from 201.140.111.58 port 63738 ssh2
...
2019-12-09 06:46:48
219.93.20.155 attackbots
2019-12-08T22:46:46.110794abusebot-2.cloudsearch.cf sshd\[9987\]: Invalid user nakagama from 219.93.20.155 port 43848
2019-12-09 06:48:10
123.148.210.188 attackbotsspam
fail2ban honeypot
2019-12-09 06:47:25
172.103.246.116 attackspambots
$f2bV_matches
2019-12-09 06:28:01
193.112.55.86 attack
$f2bV_matches
2019-12-09 06:24:53
177.73.248.35 attackbots
$f2bV_matches
2019-12-09 06:39:01
138.197.120.219 attackbots
Dec  8 17:59:52 hcbbdb sshd\[31878\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.120.219  user=root
Dec  8 17:59:54 hcbbdb sshd\[31878\]: Failed password for root from 138.197.120.219 port 44084 ssh2
Dec  8 18:05:21 hcbbdb sshd\[32579\]: Invalid user sleep from 138.197.120.219
Dec  8 18:05:21 hcbbdb sshd\[32579\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.197.120.219
Dec  8 18:05:23 hcbbdb sshd\[32579\]: Failed password for invalid user sleep from 138.197.120.219 port 53118 ssh2
2019-12-09 06:52:28
188.166.109.87 attack
2019-12-08T17:00:08.942824abusebot-5.cloudsearch.cf sshd\[23448\]: Invalid user coagadementu from 188.166.109.87 port 56280
2019-12-09 06:22:04

Recently Reported IPs

141.239.88.76 41.140.116.215 182.154.254.6 202.93.222.182
92.138.138.244 174.63.114.133 102.40.111.42 112.116.225.130
204.181.252.196 109.193.136.212 76.23.209.234 83.57.223.173
99.123.216.82 98.124.33.97 211.102.158.77 95.108.49.58
193.71.111.86 75.158.33.244 128.70.207.108 3.127.17.115