Whois & RDAP Lookup
PROXIED.COM Dedicated mobile proxies 4G/5G proxies · No caps Dedicated 4G/5G mobile proxies · Direct from trusted sellers Mobile 4G/5G · Dedicated, no sharing Uptime 99.9% · 10 countries Data Unlimited · No caps Customers 20K+ · No middlemen Free/trial Explore marketTry free211.140.192.0/18
RDAPIP Range211.140.192.0 - 211.140.255.255
Handle211.140.192.0 - 211.140.255.255
NameCMNET-liaoning
TypeALLOCATED NON-PORTABLE
CountryCN
Registered2008-09-04 06:55 UTC
Updated2021-01-20 01:08 UTC
Admin Contactcunsheng yu
Email[email protected]
Phone+86-13889888988-3150
Address6 Xinlong Street Hunnan District Shenyang, Liaoning Province, P.R.China ,110179
Tech Contactcunsheng yu
Email[email protected]
Phone+86-13889888988-3150
Address6 Xinlong Street Hunnan District Shenyang, Liaoning Province, P.R.China ,110179
Abuse Contact[email protected]
Statusactive
Registry RDAPhttps://rdap.apnic.net
Raw WHOIS response
% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html
% Information related to '211.140.192.0 - 211.140.255.255'
% Abuse contact for '211.140.192.0 - 211.140.255.255' is '[email protected]'
inetnum: 211.140.192.0 - 211.140.255.255
netname: CMNET-liaoning
descr: China Mobile Communications Corporation - liaoning company
country: CN
admin-c: CY283-AP
tech-c: CY283-AP
abuse-c: AC2006-AP
status: ALLOCATED NON-PORTABLE
remarks: ------------------------------
remarks: Please send abuse e-mail to
remarks: [email protected]
remarks: Please send probe e-mail to
remarks: [email protected]
remarks: -------------------------------
mnt-by: MAINT-CN-CMCC
mnt-lower: MAINT-CN-CMCC-liaoning
mnt-irt: IRT-CHINAMOBILE-CN
last-modified: 2021-01-20T01:08:17Z
source: APNIC
irt: IRT-CHINAMOBILE-CN
address: China Mobile Communications Corporation
address: 29, Jinrong Ave., Xicheng District, Beijing, 100032
e-mail: [email protected]
abuse-mailbox: [email protected]
admin-c: CT74-AP
tech-c: CT74-AP
auth: # Filtered
remarks: [email protected] was validated on 2026-03-23
mnt-by: MAINT-CN-CMCC
last-modified: 2026-03-23T00:47:53Z
source: APNIC
role: ABUSE CHINAMOBILECN
country: ZZ
address: China Mobile Communications Corporation
address: 29, Jinrong Ave., Xicheng District, Beijing, 100032
phone: +000000000
e-mail: [email protected]
admin-c: CT74-AP
tech-c: CT74-AP
nic-hdl: AC2006-AP
remarks: Generated from irt object IRT-CHINAMOBILE-CN
remarks: [email protected] was validated on 2026-03-23
abuse-mailbox: [email protected]
mnt-by: APNIC-ABUSE
last-modified: 2026-03-23T00:48:02Z
source: APNIC
person: cunsheng yu
nic-hdl: CY283-AP
e-mail: [email protected]
address: 6 Xinlong Street Hunnan District Shenyang, Liaoning Province, P.R.China ,110179
phone: +86-13889888988-3150
fax-no: +86-024-83781197
country: cn
mnt-by: MAINT-CN-CMCC-LIAONING
last-modified: 2008-09-04T07:32:18Z
source: APNIC
% Information related to '211.140.192.0/22AS56044'
route: 211.140.192.0/22
origin: AS56044
descr: China Mobile
29, Jinrong Ave.
mnt-by: MAINT-CN-CMCC
last-modified: 2021-12-10T04:46:56Z
source: APNIC
% This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-JP1)
% Query time: 435 msec
% WHEN: Thu Aug 06 01:57:15 UTC 2026Raw RDAP JSON (registry) https://rdap.apnic.net
{
"cidr0_cidrs": [
{
"length": 18,
"v4prefix": "211.140.192.0"
}
],
"country": "CN",
"endAddress": "211.140.255.255",
"entities": [
{
"events": [
{
"eventAction": "registration",
"eventDate": "2010-11-23T08:00:36Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-03-23T00:47:53Z"
}
],
"handle": "IRT-CHINAMOBILE-CN",
"links": [
{
"href": "https://rdap.apnic.net/entity/IRT-CHINAMOBILE-CN",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/ip/211.140.192.0/18"
}
],
"objectClassName": "entity",
"remarks": [
{
"description": [
"[email protected] was validated on 2026-03-23"
],
"title": "remarks"
}
],
"roles": [
"abuse"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-CHINAMOBILE-CN"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "China Mobile Communications Corporation\n29, Jinrong Ave., Xicheng District, Beijing, 100032"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
},
{
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T07:32:18Z"
},
{
"eventAction": "last changed",
"eventDate": "2008-09-04T07:32:18Z"
}
],
"handle": "CY283-AP",
"links": [
{
"href": "https://rdap.apnic.net/entity/CY283-AP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/ip/211.140.192.0/18"
}
],
"objectClassName": "entity",
"roles": [
"technical",
"administrative"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"cunsheng yu"
],
[
"kind",
{},
"text",
"individual"
],
[
"adr",
{
"label": "6 Xinlong Street Hunnan District Shenyang, Liaoning Province, P.R.China ,110179"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+86-13889888988-3150"
],
[
"tel",
{
"type": "fax"
},
"text",
"+86-024-83781197"
],
[
"email",
{},
"text",
"[email protected]"
]
]
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T06:55:38Z"
},
{
"eventAction": "last changed",
"eventDate": "2021-01-20T01:08:17Z"
}
],
"handle": "211.140.192.0 - 211.140.255.255",
"ipVersion": "v4",
"links": [
{
"href": "https://rdap.apnic.net/ip/211.140.192.0/18",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/ip/211.140.192.0/18"
}
],
"name": "CMNET-liaoning",
"notices": [
{
"description": [
"Objects returned came from source",
"APNIC"
],
"title": "Source"
},
{
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format."
],
"links": [
{
"href": "http://www.apnic.net/db/dbcopyright.html",
"rel": "terms-of-service",
"type": "text/html",
"value": "https://rdap.apnic.net/ip/211.140.192.0/18"
}
],
"title": "Terms and Conditions"
},
{
"description": [
"If you see inaccuracies in the results, please visit: "
],
"links": [
{
"href": "https://www.apnic.net/manage-ip/using-whois/abuse-and-spamming/invalid-contact-form",
"rel": "inaccuracy-report",
"type": "text/html",
"value": "https://rdap.apnic.net/ip/211.140.192.0/18"
}
],
"title": "Whois Inaccuracy Reporting"
}
],
"objectClassName": "ip network",
"port43": "whois.apnic.net",
"rdapConformance": [
"history_version_0",
"nro_rdap_profile_0",
"cidr0",
"rdap_level_0"
],
"remarks": [
{
"description": [
"China Mobile Communications Corporation - liaoning company"
],
"title": "description"
},
{
"description": [
"------------------------------",
"Please send abuse e-mail to",
"[email protected]",
"Please send probe e-mail to",
"[email protected]",
"-------------------------------"
],
"title": "remarks"
}
],
"startAddress": "211.140.192.0",
"status": [
"active"
],
"type": "ALLOCATED NON-PORTABLE"
}Frequently asked questions
What is WHOIS?
WHOIS is a public directory that answers "who is responsible for this?" for domains, IP ranges and ASNs. It lists registration dates, the registrar, nameservers and contacts.
What is RDAP, and how does it differ?
RDAP is the modern replacement for WHOIS. It returns the same records in a structured, consistent format. We query RDAP first and fall back to classic WHOIS text when a registry has not adopted it yet.
What is the difference between a registrar and a registrant?
The registrar is the company you register and manage a domain through, such as xTom or GoDaddy. The registrant is the person or organization that actually holds the domain.
What are nameservers?
Nameservers answer DNS questions for a domain and decide which IP addresses the name resolves to. They also show which DNS provider the domain uses.
What is DNSSEC?
DNSSEC adds cryptographic signatures to DNS answers so they cannot be quietly altered in transit. "Signed" means the domain has it enabled, "unsigned" means it does not.
Why is the contact information redacted?
Privacy laws such as GDPR require registrars to hide most personal details in public records. The abuse contact is usually still shown, so a domain or network can be reported when something goes wrong.