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

Region: Shandong

Country: China

Internet Service Provider: China Mobile

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:
% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '112.0.0.0 - 112.63.255.255'

% Abuse contact for '112.0.0.0 - 112.63.255.255' is 'abuse@chinamobile.com'

inetnum:        112.0.0.0 - 112.63.255.255
netname:        CMNET
descr:          China Mobile Communications Corporation
descr:          Mobile Communications Network Operator in China
descr:          Internet Service Provider in China
country:        CN
org:            ORG-CMCC1-AP
admin-c:        ct74-AP
tech-c:         HL1318-AP
abuse-c:        AC1895-AP
status:         ALLOCATED PORTABLE
remarks:        service provider
remarks:        --------------------------------------------------------
remarks:        To report network abuse, please contact mnt-irt
remarks:        For troubleshooting, please contact tech-c and admin-c
remarks:        Report invalid contact via www.apnic.net/invalidcontact
remarks:        --------------------------------------------------------
mnt-by:         APNIC-HM
mnt-lower:      MAINT-CN-CMCC
mnt-routes:     MAINT-CN-CMCC
mnt-irt:        IRT-CHINAMOBILE2-CN
last-modified:  2020-12-15T02:55:47Z
source:         APNIC

irt:            IRT-CHINAMOBILE2-CN
address:        China Mobile Communications Corporation
address:        29, Jinrong Ave., Xicheng District, Beijing, 100032
e-mail:         abuse@chinamobile.com
abuse-mailbox:  abuse@chinamobile.com
admin-c:        ct74-AP
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 112.6.206.139
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 17361
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;112.6.206.139.			IN	A

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

;; Query time: 30 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 06 16:57:04 CST 2026
;; MSG SIZE  rcvd: 106
Host info
Host 139.206.6.112.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
;; Got SERVFAIL reply from 183.60.83.19, trying next server
Server:		183.60.82.98
Address:	183.60.82.98#53

** server can't find 139.206.6.112.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
193.104.83.97 attackbotsspam
Unauthorized connection attempt detected from IP address 193.104.83.97 to port 2220 [J]
2020-02-03 04:05:51
36.236.137.184 attack
Honeypot attack, port: 445, PTR: 36-236-137-184.dynamic-ip.hinet.net.
2020-02-03 04:04:00
193.47.72.15 attack
Jul 30 06:45:28 ms-srv sshd[28549]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.47.72.15
Jul 30 06:45:30 ms-srv sshd[28549]: Failed password for invalid user mario from 193.47.72.15 port 42679 ssh2
2020-02-03 03:47:20
193.227.199.150 attackspam
Dec  2 03:13:53 ms-srv sshd[12807]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.227.199.150
Dec  2 03:13:55 ms-srv sshd[12807]: Failed password for invalid user ubnt from 193.227.199.150 port 39692 ssh2
2020-02-03 04:02:09
117.2.104.150 attackbots
DATE:2020-02-02 16:07:37, IP:117.2.104.150, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-03 03:42:15
92.63.194.104 attackspam
$f2bV_matches
2020-02-03 04:03:39
122.225.62.94 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-02-03 04:11:18
116.98.67.34 attackspambots
DATE:2020-02-02 16:07:36, IP:116.98.67.34, PORT:1433 MSSQL brute force auth on honeypot server (honey-neo-dc)
2020-02-03 03:44:56
193.70.38.80 attackspambots
Dec 26 03:51:02 ms-srv sshd[4639]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.70.38.80
Dec 26 03:51:04 ms-srv sshd[4639]: Failed password for invalid user aleksandr from 193.70.38.80 port 52880 ssh2
2020-02-03 03:33:50
116.102.56.169 attack
DATE:2020-02-02 18:14:25, IP:116.102.56.169, PORT:1433 - MSSQL brute force auth on a honeypot server (epe-dc)
2020-02-03 03:46:51
122.160.122.49 attackbots
Feb  2 15:39:10 work-partkepr sshd\[7615\]: Invalid user dspace from 122.160.122.49 port 38318
Feb  2 15:39:10 work-partkepr sshd\[7615\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.160.122.49
...
2020-02-03 04:09:53
78.85.81.99 attackspam
Honeypot attack, port: 445, PTR: a99.sub81.net78.udm.net.
2020-02-03 04:06:55
193.216.142.82 attackspam
Apr  5 07:52:18 ms-srv sshd[50438]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.216.142.82
Apr  5 07:52:20 ms-srv sshd[50438]: Failed password for invalid user superadmin from 193.216.142.82 port 53724 ssh2
2020-02-03 04:07:19
193.250.173.12 attackbots
Jan  9 18:01:49 ms-srv sshd[40465]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=193.250.173.12  user=root
Jan  9 18:01:51 ms-srv sshd[40465]: Failed password for invalid user root from 193.250.173.12 port 38748 ssh2
2020-02-03 03:57:00
185.3.208.182 attack
02.02.2020 16:07:15 - Bad Robot 
Ignore Robots.txt
2020-02-03 04:14:21

Recently Reported IPs

144.48.130.13 112.20.124.39 216.180.246.126 192.204.40.45
61.6.42.217 113.23.252.200 175.6.213.57 121.199.175.72
54.208.127.126 10.0.123.116 10.209.85.202 94.154.32.67
151.115.96.143 52.27.208.231 187.110.175.205 183.207.48.142
58.212.237.61 121.29.149.235 38.78.145.15 114.254.48.60