42.120.160.162

Basic Info

City: unknown

Region: unknown

Country: None

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:

Make a comment on this IP

No discussion about this IP yet. Click above link to make one.

Comments on same subnet:

IP	Type	Details	Datetime
42.120.160.121	attackspam	The IP has triggered Cloudflare WAF. CF-Ray: 54361032bca7eef6 \| WAF_Rule_ID: f6705d4933894b0583ba1042603083f6 \| WAF_Kind: firewall \| CF_Action: drop \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/2 \| Method: GET \| Host: disqus.skk.moe \| User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 YisouSpider/5.0 Safari/537.36 \| CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-12 05:49:02
42.120.160.50	attack	The IP has triggered Cloudflare WAF. CF-Ray: 5433760a38afe4c4 \| WAF_Rule_ID: f6705d4933894b0583ba1042603083f6 \| WAF_Kind: firewall \| CF_Action: drop \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/2 \| Method: GET \| Host: disqus.skk.moe \| User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 YisouSpider/5.0 Safari/537.36 \| CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-12 01:37:52
42.120.160.112	attackspam	The IP has triggered Cloudflare WAF. CF-Ray: 5415ee769a19eb51 \| WAF_Rule_ID: f6705d4933894b0583ba1042603083f6 \| WAF_Kind: firewall \| CF_Action: drop \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/1.1 \| Method: GET \| Host: theme-suka.skk.moe \| User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 YisouSpider/5.0 Safari/537.36 \| CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-08 07:21:48
42.120.160.51	attack	The IP has triggered Cloudflare WAF. CF-Ray: 541558d4fe79e7c5 \| WAF_Rule_ID: f6705d4933894b0583ba1042603083f6 \| WAF_Kind: firewall \| CF_Action: drop \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/2 \| Method: GET \| Host: disqus.skk.moe \| User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 YisouSpider/5.0 Safari/537.36 \| CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-08 02:09:18
42.120.160.123	attackbotsspam	The IP has triggered Cloudflare WAF. CF-Ray: 5416f9cdfa82e7a4 \| WAF_Rule_ID: f6705d4933894b0583ba1042603083f6 \| WAF_Kind: firewall \| CF_Action: drop \| Country: CN \| CF_IPClass: noRecord \| Protocol: HTTP/2 \| Method: GET \| Host: disqus.skk.moe \| User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 YisouSpider/5.0 Safari/537.36 \| CF_DC: LAX. Report generated by Cloudflare-WAF-to-AbuseIPDB (https://github.com/SukkaW/Cloudflare-WAF-to-AbuseIPDB).	2019-12-08 01:44:21

Whois info:

Dig info:

; <<>> DiG 9.10.3-P4-Ubuntu <<>> 42.120.160.162
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52141
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;42.120.160.162.			IN	A

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

;; Query time: 14 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Jun 30 03:42:48 CST 2022
;; MSG SIZE  rcvd: 107

Host info

162.160.120.42.in-addr.arpa domain name pointer shenmaspider-42-120-160-162.crawl.sm.cn.

Nslookup info:

Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
162.160.120.42.in-addr.arpa	name = shenmaspider-42-120-160-162.crawl.sm.cn.

Authoritative answers can be found from:

Related IP info:

Related comments:

IP	Type	Details	Datetime
182.75.139.26	attackbots	Feb 21 05:41:51 ns382633 sshd\[21639\]: Invalid user confluence from 182.75.139.26 port 19268 Feb 21 05:41:51 ns382633 sshd\[21639\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.139.26 Feb 21 05:41:53 ns382633 sshd\[21639\]: Failed password for invalid user confluence from 182.75.139.26 port 19268 ssh2 Feb 21 05:54:55 ns382633 sshd\[23357\]: Invalid user confluence from 182.75.139.26 port 13569 Feb 21 05:54:55 ns382633 sshd\[23357\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.75.139.26	2020-02-21 16:07:35
185.147.212.8	attack	[2020-02-21 02:48:39] NOTICE[1148] chan_sip.c: Registration from '' failed for '185.147.212.8:61365' - Wrong password [2020-02-21 02:48:39] SECURITY[1163] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2020-02-21T02:48:39.801-0500",Severity="Error",Service="SIP",EventVersion="2",AccountID="9104",SessionID="0x7fd82cf77db8",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.147.212.8/61365",Challenge="08b6f02d",ReceivedChallenge="08b6f02d",ReceivedHash="0046ce0b75cfd4caff8acd59d657af99" [2020-02-21 02:49:06] NOTICE[1148] chan_sip.c: Registration from '' failed for '185.147.212.8:54899' - Wrong password [2020-02-21 02:49:06] SECURITY[1163] res_security_log.c: SecurityEvent="InvalidPassword",EventTV="2020-02-21T02:49:06.167-0500",Severity="Error",Service="SIP",EventVersion="2",AccountID="2641",SessionID="0x7fd82c4c0778",LocalAddress="IPV4/UDP/192.168.244.6/5060",RemoteAddress="IPV4/UDP/185.147.212.8 ...	2020-02-21 16:07:19
103.138.61.134	attackbotsspam	MultiHost/MultiPort Probe, Scan, Hack -	2020-02-21 15:57:09
151.69.229.20	attackspam	SSH invalid-user multiple login attempts	2020-02-21 15:50:10
91.221.221.21	attackspam	(Feb 21) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=45853 TCP DPT=8080 WINDOW=3211 SYN (Feb 19) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=48483 TCP DPT=8080 WINDOW=3211 SYN (Feb 19) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=19088 TCP DPT=8080 WINDOW=3211 SYN (Feb 19) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=43158 TCP DPT=8080 WINDOW=16010 SYN (Feb 18) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=5330 TCP DPT=8080 WINDOW=3211 SYN (Feb 18) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=63058 TCP DPT=8080 WINDOW=3211 SYN (Feb 17) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=39237 TCP DPT=8080 WINDOW=3211 SYN (Feb 17) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=33279 TCP DPT=8080 WINDOW=3211 SYN (Feb 16) LEN=40 TOS=0x08 PREC=0x20 TTL=48 ID=18090 TCP DPT=8080 WINDOW=16010 SYN	2020-02-21 16:24:59
222.186.42.136	attackbots	2020-02-21T08:11:26.780509shield sshd\[17192\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.136 user=root 2020-02-21T08:11:28.646424shield sshd\[17192\]: Failed password for root from 222.186.42.136 port 14073 ssh2 2020-02-21T08:11:31.056413shield sshd\[17192\]: Failed password for root from 222.186.42.136 port 14073 ssh2 2020-02-21T08:11:33.531559shield sshd\[17192\]: Failed password for root from 222.186.42.136 port 14073 ssh2 2020-02-21T08:15:13.053852shield sshd\[17664\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.42.136 user=root	2020-02-21 16:17:31
45.133.99.2	attackbotsspam	Feb 21 08:31:27 relay postfix/smtpd\[2873\]: warning: unknown\[45.133.99.2\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 21 08:31:47 relay postfix/smtpd\[31589\]: warning: unknown\[45.133.99.2\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 21 08:32:32 relay postfix/smtpd\[31589\]: warning: unknown\[45.133.99.2\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 21 08:32:53 relay postfix/smtpd\[2877\]: warning: unknown\[45.133.99.2\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 Feb 21 08:37:27 relay postfix/smtpd\[8140\]: warning: unknown\[45.133.99.2\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6 ...	2020-02-21 15:46:25
193.56.28.100	attackspambots	Feb 21 06:55:20 heicom postfix/smtpd\[8679\]: warning: unknown\[193.56.28.100\]: SASL LOGIN authentication failed: authentication failure Feb 21 06:56:02 heicom postfix/smtpd\[8679\]: warning: unknown\[193.56.28.100\]: SASL LOGIN authentication failed: authentication failure Feb 21 06:57:01 heicom postfix/smtpd\[8677\]: warning: unknown\[193.56.28.100\]: SASL LOGIN authentication failed: authentication failure Feb 21 07:03:14 heicom postfix/smtpd\[8786\]: warning: unknown\[193.56.28.100\]: SASL LOGIN authentication failed: authentication failure Feb 21 07:05:18 heicom postfix/smtpd\[8786\]: warning: unknown\[193.56.28.100\]: SASL LOGIN authentication failed: authentication failure ...	2020-02-21 16:15:59
210.227.113.18	attackspambots	Invalid user vsftpd from 210.227.113.18 port 43200	2020-02-21 15:52:52
117.114.161.11	attackspam	Feb 21 05:54:29 debian-2gb-nbg1-2 kernel: \[4520078.666112\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:0e:18:f4:d2:74:7f:6e:37:e3:08:00 SRC=117.114.161.11 DST=195.201.40.59 LEN=40 TOS=0x00 PREC=0x00 TTL=235 ID=43601 PROTO=TCP SPT=57554 DPT=1433 WINDOW=1024 RES=0x00 SYN URGP=0	2020-02-21 16:23:13
27.106.116.63	attack	Fail2Ban Ban Triggered	2020-02-21 16:09:00
164.177.42.33	attackbots	2020-02-21T18:59:53.948204luisaranguren sshd[4023738]: Invalid user alex from 164.177.42.33 port 41114 2020-02-21T18:59:56.019843luisaranguren sshd[4023738]: Failed password for invalid user alex from 164.177.42.33 port 41114 ssh2 ...	2020-02-21 16:22:25
107.173.170.65	attackspam	Feb 20 21:50:45 kapalua sshd\[13292\]: Invalid user gitlab-prometheus from 107.173.170.65 Feb 20 21:50:45 kapalua sshd\[13292\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.170.65 Feb 20 21:50:47 kapalua sshd\[13292\]: Failed password for invalid user gitlab-prometheus from 107.173.170.65 port 44201 ssh2 Feb 20 21:54:10 kapalua sshd\[13580\]: Invalid user sunsf from 107.173.170.65 Feb 20 21:54:10 kapalua sshd\[13580\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=107.173.170.65	2020-02-21 16:03:31
157.55.39.230	attack	Automatic report - Banned IP Access	2020-02-21 16:22:51
18.221.6.250	attackbotsspam	Automatically reported by fail2ban report script (mx1)	2020-02-21 16:16:22

Recently Reported IPs

180.76.114.55	106.11.154.178	37.76.167.96	169.229.238.199
169.229.238.1	175.192.25.58	1.225.178.114	123.21.179.68
220.181.124.240	169.229.238.91	42.156.138.198	180.76.250.103
169.229.237.217	169.229.237.184	180.76.183.63	180.76.183.58
58.53.127.226	128.199.235.61	121.186.7.210	220.72.115.184