Whois & RDAP Lookup
220.181.0.0/17
RDAPRaw WHOIS response
% [whois.apnic.net] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html % Information related to '220.181.0.0 - 220.181.255.255' % Abuse contact for '220.181.0.0 - 220.181.255.255' is '[email protected]' inetnum: 220.181.0.0 - 220.181.255.255 netname: CHINANET-IDC-BJ country: CN descr: CHINANET Beijing province network descr: China Telecom descr: No.31,jingrong street descr: Beijing 100032 admin-c: CH93-AP tech-c: HC55-AP remarks: hostmaster is not for spam complaint, remarks: please send spam complaint to [email protected] mnt-by: MAINT-CHINANET mnt-lower: MAINT-CHINATELECOM-BJ status: ALLOCATED NON-PORTABLE last-modified: 2008-09-04T06:56:04Z source: APNIC person: Chinanet Hostmaster nic-hdl: CH93-AP e-mail: [email protected] address: No.31 ,jingrong street,beijing address: 100032 phone: +86-10-58501724 fax-no: +86-10-58501724 country: CN mnt-by: MAINT-CHINANET last-modified: 2022-02-28T06:53:44Z source: APNIC person: Hostmaster of Beijing Telecom corporation CHINA TELECOM nic-hdl: HC55-AP e-mail: [email protected] address: Beijing Telecom address: No. 107 XiDan Beidajie, Xicheng District Beijing phone: +86-010-58503461 fax-no: +86-010-58503054 country: cn mnt-by: MAINT-CHINATELECOM-BJ last-modified: 2008-09-04T07:29:39Z source: APNIC % This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-JP1) % Query time: 337 msec % WHEN: Mon Aug 24 23:03:15 UTC 2026
Raw RDAP JSON (registry) https://rdap.apnic.net
{
"cidr0_cidrs": [
{
"length": 16,
"v4prefix": "220.181.0.0"
}
],
"country": "CN",
"endAddress": "220.181.255.255",
"entities": [
{
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T07:29:13Z"
},
{
"eventAction": "last changed",
"eventDate": "2022-02-28T06:53:44Z"
}
],
"handle": "CH93-AP",
"links": [
{
"href": "https://rdap.apnic.net/entity/CH93-AP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/ip/220.181.0.0/17"
}
],
"objectClassName": "entity",
"roles": [
"administrative"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Chinanet Hostmaster"
],
[
"kind",
{},
"text",
"individual"
],
[
"adr",
{
"label": "No.31 ,jingrong street,beijing\n100032"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+86-10-58501724"
],
[
"tel",
{
"type": "fax"
},
"text",
"+86-10-58501724"
],
[
"email",
{},
"text",
"[email protected]"
]
]
]
},
{
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T07:29:39Z"
},
{
"eventAction": "last changed",
"eventDate": "2008-09-04T07:29:39Z"
}
],
"handle": "HC55-AP",
"links": [
{
"href": "https://rdap.apnic.net/entity/HC55-AP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/ip/220.181.0.0/17"
}
],
"objectClassName": "entity",
"roles": [
"technical"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Hostmaster of Beijing Telecom corporation CHINA TELECOM"
],
[
"kind",
{},
"text",
"individual"
],
[
"adr",
{
"label": "Beijing Telecom\nNo. 107 XiDan Beidajie, Xicheng District Beijing"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+86-010-58503461"
],
[
"tel",
{
"type": "fax"
},
"text",
"+86-010-58503054"
],
[
"email",
{},
"text",
"[email protected]"
]
]
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T06:56:04Z"
},
{
"eventAction": "last changed",
"eventDate": "2008-09-04T06:56:04Z"
}
],
"handle": "220.181.0.0 - 220.181.255.255",
"ipVersion": "v4",
"links": [
{
"href": "https://rdap.apnic.net/ip/220.181.0.0/16",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/ip/220.181.0.0/17"
}
],
"name": "CHINANET-IDC-BJ",
"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/220.181.0.0/17"
}
],
"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/220.181.0.0/17"
}
],
"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": [
"CHINANET Beijing province network",
"China Telecom",
"No.31,jingrong street",
"Beijing 100032"
],
"title": "description"
},
{
"description": [
"hostmaster is not for spam complaint,",
"please send spam complaint to [email protected]"
],
"title": "remarks"
}
],
"startAddress": "220.181.0.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.