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 free2400:4150::/31
RDAPRaw WHOIS response
% [whois.apnic.net] % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html % Information related to '2400:4000::/22' % No abuse contact registered for 2400:4000::/22 inet6num: 2400:4000::/22 netname: OCN-JPNIC-JP-20050815 descr: Japan Network Information Center country: JP admin-c: JNIC1-AP tech-c: JNIC1-AP remarks: JPNIC Allocation Block remarks: Authoritative information regarding assignments and remarks: allocations made from within this block can also be remarks: queried at whois.nic.ad.jp. To obtain an English remarks: output query whois -h whois.nic.ad.jp x.x.x.x/e remarks: ***************************************************** remarks: For abuse/any contacts regarding this address range, remarks: please refer to the contacts listed on the inet6num remarks: object displayed down below, or look up JPNIC Whois. remarks: **************************************************** mnt-by: MAINT-JPNIC mnt-lower: MAINT-JPNIC status: ALLOCATED PORTABLE last-modified: 2008-09-04T06:49:19Z source: APNIC role: Japan Network Information Center address: Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda address: Chiyoda-ku, Tokyo 101-0047, Japan country: JP phone: +81-3-5297-2311 fax-no: +81-3-5297-2312 e-mail: [email protected] admin-c: JI13-AP tech-c: JE53-AP nic-hdl: JNIC1-AP mnt-by: MAINT-JPNIC last-modified: 2022-01-05T03:04:02Z source: APNIC % Information related to '2400:4000::/22' inet6num: 2400:4000::/22 netname: OCN-CIDR-BLK-JP descr: NTT DOCOMO BUSINESS,Inc. remarks: Email address for spam or abuse complaints:[email protected] country: JP admin-c: JP00009614 tech-c: JP00009427 last-modified: 2019-02-20T22:26:42Z remarks: This information has been partially mirrored by APNIC from remarks: JPNIC. To obtain more specific information, please use the remarks: JPNIC WHOIS Gateway at remarks: http://www.nic.ad.jp/en/db/whois/en-gateway.html or remarks: whois.nic.ad.jp for WHOIS client. (The WHOIS client remarks: defaults to Japanese output, use the /e switch for English remarks: output) source: JPNIC % This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-SG1) % Query time: 438 msec % WHEN: Fri Aug 07 06:20:57 UTC 2026 % Additional information from whois.nic.ad.jp Network Information: [Network Number] 2400:4000::/22 [Network Name] [Organization] NTT DOCOMO BUSINESS,Inc. [Administrative Contact] JP00009614 [Technical Contact] JP00009427 [Abuse] [email protected] [Nameserver] ns6-tk01.ocn.ad.jp [Nameserver] ns6-tk02.ocn.ad.jp [Allocated Date] 2005/08/16 [Last Update] 2019/02/20 13:26:42(JST)
Raw RDAP JSON (registry) https://rdap.apnic.net
{
"cidr0_cidrs": [
{
"length": 22,
"v6prefix": "2400:4000::"
}
],
"country": "JP",
"endAddress": "2400:43ff:ffff:ffff:ffff:ffff:ffff:ffff",
"entities": [
{
"handle": "JP00009614",
"links": [
{
"href": "http://whois.nic.ad.jp/cgi-bin/whois_gw?key=JP00009614/e",
"hreflang": "en",
"rel": "related",
"type": "text/html",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
},
{
"href": "http://whois.nic.ad.jp/cgi-bin/whois_gw?key=JP00009614",
"hreflang": "jp",
"rel": "related",
"type": "text/html",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
}
],
"objectClassName": "entity",
"roles": [
"administrative"
]
},
{
"handle": "JP00009427",
"links": [
{
"href": "http://whois.nic.ad.jp/cgi-bin/whois_gw?key=JP00009427/e",
"hreflang": "en",
"rel": "related",
"type": "text/html",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
},
{
"href": "http://whois.nic.ad.jp/cgi-bin/whois_gw?key=JP00009427",
"hreflang": "jp",
"rel": "related",
"type": "text/html",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
}
],
"objectClassName": "entity",
"roles": [
"technical"
]
},
{
"events": [
{
"eventAction": "last changed",
"eventDate": "2022-01-05T03:04:02Z"
}
],
"handle": "JNIC1-AP",
"links": [
{
"href": "https://jpnic.rdap.apnic.net/entity/JNIC1-AP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
}
],
"objectClassName": "entity",
"roles": [
"technical",
"administrative"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Japan Network Information Center"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "Uchikanda OS Bldg 4F, 2-12-6 Uchi-Kanda\nChiyoda-ku, Tokyo 101-0047, Japan"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+81-3-5297-2311"
],
[
"tel",
{
"type": "fax"
},
"text",
"+81-3-5297-2312"
],
[
"email",
{},
"text",
"[email protected]"
]
]
]
}
],
"events": [
{
"eventAction": "last changed",
"eventDate": "2019-02-20T22:26:42Z"
}
],
"handle": "2400:4000::/22",
"ipVersion": "v6",
"links": [
{
"href": "https://jpnic.rdap.apnic.net/ip/2400:4000::/22",
"rel": "self",
"type": "application/rdap+json",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
}
],
"name": "OCN-CIDR-BLK-JP",
"notices": [
{
"description": [
"Objects returned came from source",
"JPNIC"
],
"title": "Source"
},
{
"description": [
"This is the APNIC WHOIS Database query service. The objects are in RDAP format.",
"This information has been partially mirrored by APNIC from JPNIC. To obtain more specific information, please use the JPNIC WHOIS Gateway at http://www.nic.ad.jp/en/db/whois/en-gateway.html or whois.nic.ad.jp for WHOIS client. (The WHOIS client defaults to Japanese output, use the /e switch for English output)"
],
"links": [
{
"href": "http://www.apnic.net/db/dbcopyright.html",
"rel": "terms-of-service",
"type": "text/html",
"value": "https://jpnic.rdap.apnic.net/ip/2400:4150::/31"
}
],
"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://jpnic.rdap.apnic.net/ip/2400:4150::/31"
}
],
"title": "Whois Inaccuracy Reporting"
}
],
"objectClassName": "ip network",
"port43": "whois.apnic.net",
"rdapConformance": [
"nro_rdap_profile_0",
"cidr0",
"rdap_level_0"
],
"remarks": [
{
"description": [
"NTT DOCOMO BUSINESS,Inc."
],
"title": "description"
},
{
"description": [
"Email address for spam or abuse complaints : [email protected]"
],
"title": "remarks"
}
],
"startAddress": "2400:4000::",
"status": [
"active"
],
"type": null
}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.