Autonomous System
AS26496
Last fetched
AS26496 is operated by AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, registered in US, and announces 208 prefixes to 13 BGP neighbours. AS26496 has a reputation score of 12.3 (NEUTRAL); 150 of its 865,280 announced IPv4 addresses appear on threat feeds.
Nutrition Label
Routing footprint
- Announced prefixes
- 208
- BGP neighbours
- 13
- RPKI ROAs
- 1,849
- MOAS conflicts
- 0
- CAIDA AS-rank
- 2,852
- Customer-cone ASNs
- 9
- Facilities
- 40
- Internet exchanges
- 4
- Customer degree
- 6
- Peer degree
- 59
- Provider degree
- 5
- 43.255.152.0/22
- 43.255.154.0/23
- 45.40.128.0/20
- 45.40.140.0/22
- 45.40.144.0/21
- 45.40.128.0/18
- 50.62.4.0/22
- 50.62.0.0/20
- 50.62.20.0/22
- 50.62.16.0/20
- 50.62.28.0/22
- 50.62.34.0/23
- 50.62.32.0/20
- 50.62.48.0/20
- 50.62.132.0/22
- 50.62.160.0/22
- 50.62.168.0/22
- 50.62.192.0/22
- 50.62.196.0/22
- 50.62.192.0/18
- 50.62.0.0/15
- 64.202.160.0/23
- 64.202.168.0/22
- 64.202.160.0/19
- 64.202.176.0/22
Infrastructure presence
Internet exchanges (4 total)
Facilities (40 total)
- Equinix MI1 - Miami, NOTA
- Equinix SV1/SV5/SV10 - Silicon Valley, San Jose
- Equinix DC1-DC15,DC21-DC22 - Ashburn
- CoreSite - San Jose (SV1)
- CoreSite - Los Angeles (LA1) One Wilshire
- Digital Realty Seattle SEA10
- Equinix SE2/SE3 - Seattle
- Equinix SY1/SY2 - Sydney
- Equinix HK1 - Hong Kong
- Equinix SG1 - Singapore
- CoreSite - Los Angeles (LA2)
- KOMO Plaza Seattle (Formerly Fisher Plaza)
- Equinix TY2 - Tokyo
- Intergate West / Digital.forest / Fortress
- Coresite - Milpitas (SV2)
- Equinix CU1/CU2/CU3/CU4 - Culpeper
- Equinix SG2 - Singapore
- Telehouse - Teleport Center (New York)
- Cologix MIN1
- Equinix CH3 - Elk Grove
- CoreSite - Santa Clara (SV4)
- Equinix SG3 - Singapore
- Cologix MIN2
- Centersquare Seattle (SEA1-B)
- CoreSite - Santa Clara (SV3)
Route origin authorizations
A sample of 10 of this network’s 1,849 ROAs.
- 103.1.172.0/22 · max length /24
- 103.44.220.0/24 · max length /24
- 103.87.189.0/24 · max length /24
- 103.87.190.0/23 · max length /23
- 118.139.160.0/19 · max length /24
- 148.66.128.0/19 · max length /24
- 182.50.128.0/19 · max length /24
- 2001:df1:9c00::/48 · max length /48
- 203.124.96.0/19 · max length /24
- 2403:bc80::/32 · max length /32
Upstreams
The networks that most often share an observed BGP path with AS26496.
Blast radius
- Announced IPv4 addresses
- 865,280
- Threat-listed addresses
- 150
- Threat density
- 0.0173 %
- Routed prefixes
- 190
How much of the internet this network is responsible for, and how much of that address space currently appears on a threat feed. Coverage: computed.
Peering ecosystem
A sample of 13 of this network’s 13 BGP neighbours.
- TWELVE99 - Arelion Sweden AB · AS1299
- NTT-DATA-2914 - NTT America, Inc. · AS2914
- DTAG - Deutsche Telekom AG · AS3320
- AS6453 - TATA COMMUNICATIONS (AMERICA) INC · AS6453
- HURRICANE - Hurricane Electric LLC · AS6939
- AARNET-AS-AP - Australian Academic and Research Network (AARNet) · AS7575
- MTS - MTS PJSC · AS8359
- CONVERGE-AS - Converge ICT Solutions Inc. · AS17639
- GO-DADDY-COM-LLC - GoDaddy.com, LLC · AS398101
- GO-DADDY-COM-LLC - GoDaddy.com, LLC · AS398785
- GO-DADDY-COM-LLC - GoDaddy.com, LLC · AS400748
- GO-DADDY-COM-LLC - GoDaddy.com, LLC · AS400749
- GO-DADDY-COM-LLC - GoDaddy.com, LLC · AS400754
Reputation
12.3reputation score (NEUTRAL)
AS26496 (AS-26496-GO-DADDY-COM-LLC - GoDaddy.com, LLC, US) has a reputation score of 65.4 (NEUTRAL).
- Threat density
- 60.3/100
- Graph metrics
- 90.0/100
- Historical behaviour
- 75.0/100
- Prefix age
- 20.0/100
These are reputation signals about the network as a whole, not a threat-feed verdict about a specific address.
Registration
- Registered to
- GoDaddy.com, LLC
- RIR
- ARIN
- Registered
- Tue, 01 Oct 2002 10:31:58 GMT
- Abuse contact
- abuse@godaddy.com
This is the abuse contact WhisperGraph holds for the network.
Threat-feed evidence
Related pages
Pivot from AS26496 into the prefixes, peers and country it routes for.
Queries
This ASN's full card — routing footprint, peers, conflicts and RIR facts.
MATCH (a:ASN {name: $asn})
OPTIONAL MATCH (a)-[:HAS_NAME]->(an:ASN_NAME)
OPTIONAL MATCH (a)-[:HAS_COUNTRY]->(co:COUNTRY)
OPTIONAL MATCH (a)-[:REGISTERED_BY]->(org:ORGANIZATION)
WITH a,
collect(an.name) AS operatorNames,
collect(co.name) AS countries,
collect(org.name) AS organizations
OPTIONAL MATCH (a)-[:ROUTES]->(prefix:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations,
collect(prefix.name)[0..25] AS samplePrefixes
OPTIONAL MATCH (a)-[:BGP_NEIGHBOR]-(peer:ASN)
OPTIONAL MATCH (peer)-[:HAS_NAME]->(peern:ASN_NAME)
WITH a, operatorNames, countries, organizations, samplePrefixes,
collect({asn: peer.name, operator: peern.name})[0..25] AS samplePeers
OPTIONAL MATCH (a)<-[:CONFLICTS_WITH]-(conflict:ANNOUNCED_PREFIX)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers,
collect(conflict.name)[0..25] AS sampleConflicts
OPTIONAL MATCH (a)-[:HAS_SIGNAL]->(sig:THREAT_SIGNAL_TYPE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts,
collect(DISTINCT sig.name) AS signals
OPTIONAL MATCH (a)-[:IX_MEMBER]->(ix:INTERNET_EXCHANGE)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals,
collect({id: ix.id, name: ix.name})[0..25] AS sampleExchanges
OPTIONAL MATCH (a)-[:AS_PRESENT_AT]->(fac:FACILITY)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges,
collect({id: fac.id, name: fac.name})[0..25] AS sampleFacilities
OPTIONAL MATCH (roa:ROA)-[:ROA_AUTHORIZES_ORIGIN]->(a)
WITH a, operatorNames, countries, organizations, samplePrefixes, samplePeers, sampleConflicts, signals, sampleExchanges, sampleFacilities,
collect({prefix: roa.prefix, maxLength: roa.maxLength})[0..10] AS sampleRoas
CALL { WITH a MATCH (a)-[:ROUTES]->(p:ANNOUNCED_PREFIX) RETURN count(p) AS prefixCount }
CALL { WITH a MATCH (a)-[:BGP_NEIGHBOR]-(n:ASN) RETURN count(n) AS peerCount }
CALL { WITH a MATCH (a)<-[:CONFLICTS_WITH]-(c:ANNOUNCED_PREFIX) RETURN count(c) AS conflictCount }
CALL { WITH a MATCH (a)-[:ROA_AUTHORIZES_ORIGIN]-(r:ROA) RETURN count(r) AS roaCount }
CALL { WITH a MATCH (a)-[:AS_PRESENT_AT]->(f:FACILITY) RETURN count(f) AS facilityCount }
CALL { WITH a MATCH (a)-[:IX_MEMBER]->(x:INTERNET_EXCHANGE) RETURN count(x) AS ixpCount }
RETURN a.name AS name,
a.rir AS rir,
a.orgName AS orgName,
a.asRank AS asRank,
a.coneAsns AS coneAsns,
a.conePrefixes AS conePrefixes,
a.coneAddresses AS coneAddresses,
a.registrationDate AS registrationDate,
a.reputationScore AS reputationScore,
a.reputationCategory AS reputationCategory,
a.overallThreatLevel AS overallThreatLevel,
a.abuseEmail AS abuseEmail,
a.hijackPostureScore AS hijackPostureScore,
a.hijackOriginMismatchCount AS hijackOriginMismatchCount,
a.routeLeakCount AS routeLeakCount,
a.routeLeakTypes AS routeLeakTypes,
a.degreeCustomer AS degreeCustomer,
a.degreePeer AS degreePeer,
a.degreeProvider AS degreeProvider,
operatorNames, countries, organizations,
samplePrefixes, samplePeers, sampleConflicts,
signals, sampleExchanges, sampleFacilities, sampleRoas,
prefixCount, peerCount, conflictCount, roaCount, facilityCount, ixpCountRun yourself →The five networks that most often share this ASN's observed BGP paths.
MATCH (a:ASN {name: $asn})<-[:BGP_PATH]-(b:BGP_PATH_OBSERVATION)
WITH b LIMIT 200
MATCH (b)-[:BGP_PATH]->(up:ASN)
WHERE up.name <> $asn
WITH up.name AS asn, count(*) AS observations
ORDER BY observations DESC
LIMIT 5
RETURN asn, observationsRun yourself →Or query Whisper from your own LLM workflow via the Whisper MCP server.