Autonomous system
AS14778 YAHOO
Unclassified ARIN
Summary
Yahoo Holdings
enterprise business infrastructure
Nine IPv6 blocks from three continents, every one numbered from the same slice.
What it's used for
- Corporate and office network space for a large internet company. 1,536 IPv4 addresses across five prefixes, nine IPv6 prefixes, and two observed BGP neighbours.
Notable
- The IPv6 announcements come from three unrelated ranges,
2001:4998:ef6f::/48,2406:6e00:ef98::/48and2a00:1288:efc1::/48among them, and every one of the nine carriesefin the same position. - Registry records span three regions:
A-YAHOO-US11,CH-YAHOO, andYAHOOTWCICandYAHOOISNET-AS-APwith an incident response team named as contact. - All fifteen sampled addresses answered. Thirteen returned the identical name
unknown.yahoo.com. - The two exceptions are
temp-clearpass1.net.corp.tw1.yahoo.comandnat-vpn-users9.cfw-a-usr.net.tw1.fy94.net.
Interesting
- The shared marker across nine blocks is one internal numbering plan applied on top of address space obtained from three different registries. The company decided what its own blocks would be called and then made the regional allocations fit, which is the sort of discipline only an organisation with a global addressing team manages.
- One wildcard name on every address is a reasonable way to publish nothing, and the two names that escaped it are more revealing than the thousands that did not. One marks a network access control appliance labelled as temporary; the other is a shared address for staff on the corporate virtual private network, published under an unbranded domain that gives no hint of the company.
- Naming a security incident team as registry contact on the regional records is the practice a network this size should follow everywhere.
This description is AI-generated, best-effort context — not authoritative, and provided without any guarantee of accuracy. Source, and how to suggest an edit.
Interconnection
Peering at a glance
Internet exchanges
No exchange port on file. Many exchanges publish no participant list, so this is not proof of absence.
Exchange presence is recorded rather than inferred: the directory collected by Packet Clearing House (https://www.pch.net/ixp/data) on 2026-10-20, licensed CC BY-NC-SA 3.0. Transit is inferred from observed BGP paths, never declared by either party.
Address space
Summary
IPv4 5 prefixes · 1.54K addresses IPv6 9 prefixes
| Country | Name | Prefixes |
|---|---|---|
| US | United States of America | 14 |
Registry
Allocation record
- Registry
- ARIN
- Handle
AS14776- Registry name
- YAHOO
- Registrant
- Yahoo Holdings Inc.
- Abuse contact
- rir-abuse@yahooinc.com
- Registered
- 2000-02-07
- Last changed
- 2020-07-21
- Allocation
- assigned
Routing security
RPKI and IRR
- RPKI
- 0% valid · 0 valid, 15 with no ROA
- ROAs
- 0 authorising AS14778
- ASPA
- no ASPA record
- IRR
- 40% registered · 6 of 15 announcements 4 other origin
- Route objects
- 62 naming AS14778
Reputation
Classification and threat
Unclassified Not in the curated lists. Most of the ~80,000 allocated ASNs are not.
Spamhaus DROP
Not on ASN-DROP The network as a whole is not listed.
No DROP prefixes None of its announced space is on the DROP prefix list.
Spamhaus DROP ("Don't Route Or Peer") lists space and networks run by, or hijacked for, spam and cybercrime operations: 442 networks and 1,778 prefixes, as published 2026-10-20. A short, high-confidence list, so a match is worth taking seriously, and absence from it says little on its own.
FBI IC3
No IC3 indicators Nothing from the FBI IC3 feed.
IC3 threat data is alpha. Absence of an indicator is not evidence of good behaviour, only of absence from this one feed.
Elsewhere