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

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

;; QUESTION SECTION:
;42.195.21.158.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 04 14:43:52 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 158.21.195.42.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 158.21.195.42.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
176.223.11.22 attack
NAME : DIGITAL-CABLE-SYSTEMS-SA CIDR : 176.223.0.0/19 SYN Flood DDoS Attack Romania - block certain countries :) IP: 176.223.11.22  Denial-of-Service Attack (DoS) Detected and Blocked by ADMIN  - data recovery https://help-dysk.pl
2019-07-25 10:33:09
200.209.174.76 attackspam
Jul 24 21:51:50 vtv3 sshd\[25386\]: Invalid user taiga from 200.209.174.76 port 56651
Jul 24 21:51:50 vtv3 sshd\[25386\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
Jul 24 21:51:52 vtv3 sshd\[25386\]: Failed password for invalid user taiga from 200.209.174.76 port 56651 ssh2
Jul 24 22:00:33 vtv3 sshd\[30098\]: Invalid user lara from 200.209.174.76 port 59556
Jul 24 22:00:33 vtv3 sshd\[30098\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
Jul 24 22:14:04 vtv3 sshd\[4435\]: Invalid user postgres from 200.209.174.76 port 48525
Jul 24 22:14:04 vtv3 sshd\[4435\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.209.174.76
Jul 24 22:14:06 vtv3 sshd\[4435\]: Failed password for invalid user postgres from 200.209.174.76 port 48525 ssh2
Jul 24 22:18:27 vtv3 sshd\[6660\]: Invalid user sysbackup from 200.209.174.76 port 35436
Jul 24 22:18:27 vtv3 sshd\[
2019-07-25 11:03:54
141.98.81.254 attack
3389BruteforceFW23
2019-07-25 11:07:56
59.145.221.103 attackspam
Jul 25 04:48:15 eventyay sshd[18544]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103
Jul 25 04:48:17 eventyay sshd[18544]: Failed password for invalid user test from 59.145.221.103 port 57677 ssh2
Jul 25 04:55:37 eventyay sshd[20229]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=59.145.221.103
...
2019-07-25 11:11:46
209.17.96.122 attackspam
Port scan attempt detected by AWS-CCS, CTS, India
2019-07-25 11:05:37
185.176.27.110 attackspambots
Splunk® : port scan detected:
Jul 24 23:04:49 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=185.176.27.110 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=33866 PROTO=TCP SPT=55388 DPT=3335 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-25 11:06:07
129.28.149.218 attackbots
Jul 25 04:32:01 dedicated sshd[22863]: Invalid user usuario from 129.28.149.218 port 59280
2019-07-25 10:47:38
95.213.177.122 attack
" "
2019-07-25 10:42:45
79.111.15.142 attackbots
Splunk® : port scan detected:
Jul 24 22:10:53 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:64:c3:d6:0b:ef:f0:08:00 SRC=79.111.15.142 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=54510 PROTO=TCP SPT=44238 DPT=3389 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-25 10:45:19
2.139.209.78 attackbots
2019-07-25T02:43:06.427430abusebot-7.cloudsearch.cf sshd\[23094\]: Invalid user bishop from 2.139.209.78 port 41032
2019-07-25 10:51:53
207.180.236.126 attack
Splunk® : port scan detected:
Jul 24 18:59:45 testbed kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=82:c6:52:d1:6e:53:c0:42:d0:39:2c:30:08:00 SRC=207.180.236.126 DST=104.248.11.191 LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=17745 PROTO=TCP SPT=40078 DPT=5060 WINDOW=1024 RES=0x00 SYN URGP=0
2019-07-25 09:53:52
43.230.144.18 attack
Unauthorised access (Jul 25) SRC=43.230.144.18 LEN=40 TTL=244 ID=25571 TCP DPT=445 WINDOW=1024 SYN
2019-07-25 10:47:03
37.139.2.218 attackbots
Jul 25 03:29:17 mail sshd\[1771\]: Failed password for invalid user master from 37.139.2.218 port 50982 ssh2
Jul 25 03:45:52 mail sshd\[2184\]: Invalid user bonaka from 37.139.2.218 port 33568
...
2019-07-25 10:58:22
115.135.9.168 attackspam
Autoban   115.135.9.168 AUTH/CONNECT
2019-07-25 11:04:56
202.191.120.225 attackbotsspam
Unauthorized connection attempt from IP address 202.191.120.225 on Port 445(SMB)
2019-07-25 09:54:21

Recently Reported IPs

33.131.100.41 146.95.238.107 79.127.80.132 138.96.249.248
155.124.46.204 200.124.136.195 204.250.135.156 171.241.146.197
15.170.170.128 175.197.133.205 168.186.82.238 163.102.73.32
41.51.92.88 222.38.219.77 206.231.22.96 28.100.101.71
184.187.215.171 175.218.50.192 87.23.185.231 158.118.74.165