LINE IP Ranges
LINE is the messaging service operated by LY Corporation, the company Z Holdings and its subsidiaries - LINE Corporation and Yahoo Japan among them - merged into on 1 October 2023. Its network is AS38631, whose aut-num carries the AS name LINE and the description LY Corporation, and whose authoritative record sits in JPNIC rather than in APNIC.
- Provider
- LINE
- Primary ASN
- AS38631
- Category
- Tech
- Headquarters
- Tokyo, Japan
- Announced IPv4 prefixes
- 147
- Registry
- APNIC
Known IP ranges
These prefixes are currently announced to the global routing table by AS38631 (LINE - LY Corporation). Prefix sets change over time - use WHOIS Lookup for the authoritative record on any specific address.
43.223.0.0/16
147.92.128.0/17
203.104.128.0/20
203.104.144.0/21
203.104.152.0/22
119.235.236.0/23
103.2.30.0/23
203.104.156.0/23
43.223.17.0/24
147.92.253.0/24
2400:dcc0::/32
2400:dcc0:a205::/48
2400:dcc0:a805::/48 (IPv6)
What does an LINE IP mean in a privacy test?
An AS38631 address is one of LINE's own machines rather than a subscriber line or rented compute, so seeing one means you reached LINE, not that anything of yours was routed through it. It proves little in the other direction, because much of the product answers from Amazon CloudFront and Akamai instead.
LINE does not publish its platform IP addresses
This is the direct answer to the search that brings people here, and it is unusually direct because LINE states it on the record rather than simply never getting round to a file. Its developer FAQ takes the question in the form people actually ask it - whether the IP address of the LINE Platform is public, so that a bot server can be restricted to it - and answers that no, the address a webhook is sent from is not disclosed, and that signature validation should be used instead of access control by IP address. The Messaging API development guidelines repeat that LINE does not disclose the IP addresses of the LINE Platform and add the reason any hardcoded firewall rule would rot anyway: those addresses are subject to change without notice. What LINE points you at instead is the x-line-signature request header, a digest of the request body that your own server recomputes and compares.
That leaves the registry as the only checkable source, and for this network the registry is JPNIC rather than APNIC. The aut-num carries the AS name LINE and the description LY Corporation, and the copy APNIC serves is marked as only partially mirrored from JPNIC, with a remark referring specific queries to whois.nic.ad.jp or the JPNIC WHOIS gateway. Asking APNIC RDAP for the number returns the assignment block AS38627 - AS38656, labelled JPNIC-2Byte-ASBLOCK-AP and described as being for assignment to JPNIC members, so the 2008 registration date on that response belongs to the block and not to LINE. On the address side the announced IPv4 space collapses to thirteen aggregates rather than the handful usually quoted: the largest are 43.223.0.0/16, 147.92.128.0/17, 203.104.128.0/20 and 203.104.144.0/21, and the rest are smaller blocks inside 203.104.128.0/18, 103.2.28.0/22 and 119.235.224.0/19. In the copy APNIC mirrors, each of those objects is ALLOCATED PORTABLE, described as LY Corporation at 1-3 Kioicho, Chiyoda-ku, Tokyo, and pointed at ml-backbone-contact@lycorp.co.jp for abuse. No object checked, in either copy, carries a geofeed, so any city attached to a LINE address is a commercial database making its own inference.
What an AS38631 address is, and why WHOIS can say Yahoo
Nothing on AS38631 is sold as hosting, so unlike a cloud or hosting range there is no customer machine here to mistake for the operator. An address in this space is LINE's own infrastructure answering a client: an inbound connection from these blocks is LINE fetching or delivering something, and an outbound connection to them is an app or an integration talking to the platform. It is not somewhere a VPN or a proxy exits from. Reverse DNS will rarely settle it for you either, because most of the space has no delegation to read - addresses sampled across 147.92.128.0/17, 43.223.0.0/16 and 203.104.128.0/20 return NXDOMAIN, while 203.104.134.1 does answer as nw.linecorp.com.
The name on the paperwork is what trips people up, and which name you get depends on which copy of the registry answers. In the authoritative JPNIC record the assignments read network name LINE and organization LINE Corporation, sitting inside allocations held by LY Corporation, while 43.223.0.0/16 reads LY and LY Corporation instead. The partial copy APNIC mirrors flattens all of them to the netname YAHOO with the description LY Corporation, which is why a WHOIS client that stops at APNIC reports Yahoo on a LINE address. That result is a mirroring artefact rather than a misrouted lookup, and whois.nic.ad.jp settles it. The second caveat is the one that actually costs people time: a match proves the network, but a miss proves nothing, because much of the product does not run on it. line.me resolves inside 147.92.128.0/17, yet www.line.me resolves through Amazon CloudFront and api.line.me through Akamai, which means genuine LINE traffic routinely arrives from AS16509 or AS16625 instead of from AS38631.
Related tools
Frequently asked questions
What IP ranges does LINE use?
LINE announces its space under AS38631, registered through JPNIC with the AS name LINE and the description LY Corporation. Its announced IPv4 space collapses to thirteen aggregates, the largest being 43.223.0.0/16 and 147.92.128.0/17, followed by 203.104.128.0/20 and 203.104.144.0/21, with the rest in smaller blocks inside 203.104.128.0/18, 103.2.28.0/22 and 119.235.224.0/19; the current announced-prefix count is in the table on this page. It is a compact network for a service of this size - when this page was checked on 23 August 2026, RIPEstat put the announced space at 147 IPv4 prefixes covering 108,288 distinct addresses, plus 116 IPv6 prefixes, which is a corporate estate rather than a carrier's.
Why does a LINE IP appear in my privacy test?
An AS38631 address is one of LINE's own machines rather than a subscriber line or rented compute, so finding one in a lookup means you reached LINE, not that anything of yours was routed through it. The address a LINE user shows the world is still their mobile carrier's or their VPN's, because none of this space is handed out to people using the app. A match also proves less than it looks: line.me resolves into this network, but www.line.me and api.line.me answer from Amazon CloudFront and Akamai addresses instead, so a great deal of genuine LINE traffic never touches AS38631 at all.
Does LINE publish a list of its IP addresses?
No, and it says so explicitly. The LINE Developers FAQ answers the question of whether the IP address of the LINE Platform is public by stating that the address a webhook is sent from is not disclosed, and recommending signature validation instead of access control by IP address. The Messaging API development guidelines add that the addresses are subject to change without notice. The supported way to verify that a request really came from the platform is the x-line-signature header, not a firewall rule.
Why does a WHOIS lookup on a LINE IP address say Yahoo?
Because you are reading APNIC's partial mirror rather than the authoritative record. APNIC labels these objects with the netname YAHOO and the description LY Corporation. Query JPNIC directly, at whois.nic.ad.jp or through its WHOIS gateway, and the same assignments come back as network name LINE, organization LINE Corporation, sitting inside allocations held by LY Corporation - except 43.223.0.0/16, which reads LY and LY Corporation. The AS name is LINE in both copies. Nothing is misrouted; the two copies simply carry different labels.
How do I check whether an address really belongs to LINE?
Look up the origin ASN and see whether it is AS38631, then confirm against the registry. Because APNIC serves only a partial mirror, the authoritative record is the JPNIC gateway at whois.nic.ad.jp, where the blocks come back as network name LINE or LY under LY Corporation allocations; APNIC's copy of the same blocks shows them as ALLOCATED PORTABLE with the netname YAHOO. What that check cannot do is rule LINE out: line.me resolves inside 147.92.128.0/17 on AS38631, but www.line.me answers from Amazon CloudFront and api.line.me from Akamai, so traffic that genuinely belongs to the service often originates on AS16509 or AS16625.