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 freeAS9824
RDAPHandleAS9824
NameJTCL-JP-AS
HolderJCOM Co., Ltd.
CountryJP
Registered2008-09-04 06:40 UTC
Updated2021-10-18 23:16 UTC
RegistrantJCOM Co., Ltd.
Email[email protected]
Phone+81-3-4366-8870
Address1-2-1, Kamiogi, Suginami-ku, Tokyo, Japan, 167-0043
Admin ContactJupiter Telecommunication Co Ltd administrator
Email[email protected]
Phone+81-3-6765-8000
Address1-2-1, Kamiogi,Suginami-ku, Tokyo, Japan, 167-0043
Tech ContactJupiter Telecommunication Co Ltd administrator
Email[email protected]
Phone+81-3-6765-8000
Address1-2-1, Kamiogi,Suginami-ku, Tokyo, Japan, 167-0043
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 'AS9249 - AS10239' as-block: AS9249 - AS10239 descr: APNIC ASN block remarks: These AS numbers are further assigned by APNIC remarks: to APNIC members and end-users in the APNIC region admin-c: HM20-AP tech-c: HM20-AP mnt-by: APNIC-HM mnt-lower: APNIC-HM last-modified: 2022-09-22T22:36:45Z source: APNIC role: APNIC Hostmaster address: P.O. BOX 2131 address: 4101 QLD country: AU phone: +61 7 3858 3100 fax-no: +61 7 3858 3199 e-mail: [email protected] admin-c: AMS11-AP tech-c: AH256-AP nic-hdl: HM20-AP remarks: Administrator for APNIC notify: [email protected] mnt-by: MAINT-APNIC-AP last-modified: 2026-08-14T00:28:10Z source: APNIC % Information related to 'AS9824' % Abuse contact for 'AS9824' is '[email protected]' aut-num: AS9824 as-name: JTCL-JP-AS descr: JCOM Co., Ltd. country: JP org: ORG-JTCL1-AP admin-c: JTCL2-AP tech-c: JTCL2-AP abuse-c: AJ428-AP mnt-lower: MAINT-JTCL-JP mnt-routes: MAINT-JTCL-JP mnt-by: APNIC-HM mnt-irt: IRT-JTCL-JP last-modified: 2021-10-18T23:16:54Z source: APNIC irt: IRT-JTCL-JP address: 1-2-1, Kamiogi, Suginami-ku address: Tokyo, Japan, 167-0043 e-mail: [email protected] abuse-mailbox: [email protected] admin-c: JTCL2-AP tech-c: JTCL2-AP auth: # Filtered remarks: [email protected] was validated on 2026-05-28 mnt-by: MAINT-JTCL-JP last-modified: 2026-06-05T07:03:20Z source: APNIC organisation: ORG-JTCL1-AP org-name: JCOM Co., Ltd. org-type: LIR country: JP address: 1-2-1, Kamiogi, Suginami-ku address: Tokyo, Japan, 167-0043 phone: +81-3-4366-8870 fax-no: +81-3-4366-8571 e-mail: [email protected] mnt-ref: APNIC-HM mnt-by: APNIC-HM last-modified: 2023-09-05T02:16:29Z source: APNIC role: ABUSE JTCLJP country: ZZ address: 1-2-1, Kamiogi, Suginami-ku address: Tokyo, Japan, 167-0043 phone: +000000000 e-mail: [email protected] admin-c: JTCL2-AP tech-c: JTCL2-AP nic-hdl: AJ428-AP remarks: Generated from irt object IRT-JTCL-JP remarks: [email protected] was validated on 2026-05-28 abuse-mailbox: [email protected] mnt-by: APNIC-ABUSE last-modified: 2026-05-28T06:49:09Z source: APNIC role: Jupiter Telecommunication Co Ltd administrator address: 1-2-1, Kamiogi,Suginami-ku address: Tokyo, Japan, 167-0043 country: JP phone: +81-3-6765-8000 e-mail: [email protected] admin-c: JTCL2-AP tech-c: JTCL2-AP nic-hdl: JTCL2-AP mnt-by: MAINT-JTCL-JP last-modified: 2025-07-01T05:25:52Z source: APNIC % This query was served by the APNIC Whois Service version 1.88.48 (WHOIS-JP1) % Query time: 331 msec % WHEN: Fri Aug 14 07:16:42 UTC 2026
Raw RDAP JSON (registry) https://rdap.apnic.net
{
"country": "JP",
"endAutnum": 9824,
"entities": [
{
"events": [
{
"eventAction": "registration",
"eventDate": "2014-12-31T02:31:16Z"
},
{
"eventAction": "last changed",
"eventDate": "2025-07-01T05:25:52Z"
}
],
"handle": "JTCL2-AP",
"links": [
{
"href": "https://rdap.apnic.net/entity/JTCL2-AP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/autnum/9824"
}
],
"objectClassName": "entity",
"roles": [
"technical",
"administrative"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"Jupiter Telecommunication Co Ltd administrator"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "1-2-1, Kamiogi,Suginami-ku\nTokyo, Japan, 167-0043"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+81-3-6765-8000"
],
[
"email",
{},
"text",
"[email protected]"
]
]
]
},
{
"events": [
{
"eventAction": "registration",
"eventDate": "2014-12-31T02:31:20Z"
},
{
"eventAction": "last changed",
"eventDate": "2026-06-05T07:03:20Z"
}
],
"handle": "IRT-JTCL-JP",
"links": [
{
"href": "https://rdap.apnic.net/entity/IRT-JTCL-JP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/autnum/9824"
}
],
"objectClassName": "entity",
"remarks": [
{
"description": [
"[email protected] was validated on 2026-05-28"
],
"title": "remarks"
}
],
"roles": [
"abuse"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"IRT-JTCL-JP"
],
[
"kind",
{},
"text",
"group"
],
[
"adr",
{
"label": "1-2-1, Kamiogi, Suginami-ku\nTokyo, Japan, 167-0043"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"email",
{},
"text",
"[email protected]"
],
[
"email",
{
"pref": "1"
},
"text",
"[email protected]"
]
]
]
},
{
"events": [
{
"eventAction": "registration",
"eventDate": "2017-08-08T23:29:03Z"
},
{
"eventAction": "last changed",
"eventDate": "2023-09-05T02:16:29Z"
}
],
"handle": "ORG-JTCL1-AP",
"links": [
{
"href": "https://rdap.apnic.net/entity/ORG-JTCL1-AP",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/autnum/9824"
}
],
"objectClassName": "entity",
"roles": [
"registrant"
],
"vcardArray": [
"vcard",
[
[
"version",
{},
"text",
"4.0"
],
[
"fn",
{},
"text",
"JCOM Co., Ltd."
],
[
"kind",
{},
"text",
"org"
],
[
"adr",
{
"label": "1-2-1, Kamiogi, Suginami-ku\nTokyo, Japan, 167-0043"
},
"text",
[
"",
"",
"",
"",
"",
"",
""
]
],
[
"tel",
{
"type": "voice"
},
"text",
"+81-3-4366-8870"
],
[
"tel",
{
"type": "fax"
},
"text",
"+81-3-4366-8571"
],
[
"email",
{},
"text",
"[email protected]"
]
]
]
}
],
"events": [
{
"eventAction": "registration",
"eventDate": "2008-09-04T06:40:30Z"
},
{
"eventAction": "last changed",
"eventDate": "2021-10-18T23:16:54Z"
}
],
"handle": "AS9824",
"links": [
{
"href": "https://rdap.apnic.net/autnum/9824",
"rel": "self",
"type": "application/rdap+json",
"value": "https://rdap.apnic.net/autnum/9824"
}
],
"name": "JTCL-JP-AS",
"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/autnum/9824"
}
],
"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/autnum/9824"
}
],
"title": "Whois Inaccuracy Reporting"
}
],
"objectClassName": "autnum",
"port43": "whois.apnic.net",
"rdapConformance": [
"history_version_0",
"nro_rdap_profile_0",
"nro_rdap_profile_asn_hierarchical_0",
"cidr0",
"rdap_level_0"
],
"remarks": [
{
"description": [
"JCOM Co., Ltd."
],
"title": "description"
}
],
"startAutnum": 9824,
"status": [
"active"
]
}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.