Noname Security API users list

Email list of companies using Noname Security API

Q: How many companies use Noname Security API?

Data InfoMetrix tracks 4,003 companies using Noname Security API, with 18,020 verified contacts at those accounts as of October 2026. The largest groups are Banking & Fintech, Retail and Healthcare. Counts are estimates from our database and market research, so ask us for a live count for your exact criteria.

Q: Who buys and manages Noname Security API inside a company?

Noname Security API is usually owned by API Security (Akamai). Decision-makers include CISO, VP of Engineering and Head of Application Security; AppSec Engineering Manager and DevSecOps Lead shape the choice, and Software Engineers and AppSec Engineers use it day to day. Our Noname Security API list can include any of these roles.

Q: Which Noname Security API products or editions can I target?

You can target accounts by the Noname Security API products they run, including Noname API Discovery, Noname Posture Management, Noname Runtime Protection, Noname Active Testing and Akamai API Security. Tell us which edition or module matters and we filter the list to those accounts.

Q: What other software do Noname Security API customers use?

Noname Security API customers commonly also run Akamai, AWS, Kong, Apigee and Jira. Noname Security API is often connected to AWS API Gateway, so users of those tools overlap heavily. We can filter any list by this kind of stack overlap.

Q: What are the main alternatives to Noname Security API?

The main alternatives to Noname Security API are Salt Security, Traceable and Wallarm. We also keep verified user lists for Salt Security, which is useful for competitive displacement campaigns.

Q: When are Noname Security API customers most likely to buy?

Buying triggers we track for Noname Security API accounts include API breach in sector, open banking rollout, API gateway change and New AppSec leader. A common pain point is shadow and zombie APIs: Undocumented APIs leak data.

Q: Can Data InfoMetrix deliver a free sample Noname Security contact list before ordering?

Yes. Data InfoMetrix delivers a complimentary 10-record sample tailored to your target Noname Security criteria—including target job titles, company size, and region—delivered within one business day with no obligation.

Q: How does Data InfoMetrix guarantee email deliverability for Noname Security contacts?

Data InfoMetrix provides a 99% email deliverability guarantee on all Noname Security datasets. Every contact record undergoes real-time email verification within a 30 to 45-day refresh cycle, backed by a 1:1 hard bounce replacement policy for 30 days after delivery.

Reach application security and API platform leaders using Noname Security, now Akamai API Security, for API discovery, posture and testing.

4,003+Companies

18,020+Contacts

Updated Oct 7, 2026GDPR · CCPA99% accuracy

See sample data

Free Noname Security API count + 10 sample records

4,003+ companies · 18,020+ contacts available

✓Exact count for your titles, regions and company size
✓10 verified sample records to check quality
✓Price quote within 1 business day

Trusted by B2B and enterprise revenue teams

How many companies use Noname Security API?

Data InfoMetrix tracks 4,003+ companies running Noname Security API as of October 2026, with 18,020+ verified contacts at those accounts. The largest groups are Banking & Fintech, Retail and Healthcare. Buying decisions usually sit with the CISO, VP of Engineering and Head of Application Security. Counts are estimates built from technology footprint scans, job-post signals and partner directories, checked by our research team. How we count

Tracked accounts4,003+

Organizations detected running Noname Security API.

Verified contacts18,020+

Direct emails and phone dials for decision-makers.

Primary personasHead of Application Security, CISO, API Platform Owner

Full buying committee mapped.

Deliverability SLA99%

SMTP-verified, with 1:1 replacement of any email that hard bounces within 30 days.

Data specification · Updated Q4 2026

Technology category	Cybersecurity
Tracked organizations	4,003+ verified accounts worldwide
Decision-maker contacts	18,020+ records with emails, mobile and direct dials
Key roles	Head of Application Security, CISO, API Platform Owner, platform administrators, IT directors, procurement
Geography	180+ countries · country-by-country counts on request
Verification	DNS and script telemetry, 5-stage SMTP handshake, manual research
Refresh cadence	Continuous, 30–45 day maximum record age at delivery
Compliance	GDPR, CAN-SPAM, CCPA and CASL
Delivery	24–48 hours as CSV, XLSX or CRM API

Editorial & verification

Researched by the Data InfoMetrix research team. Counts updated October 2026.

How we count and verify data

Size your Noname Security API audience

Pick a region, company size and buying role to estimate how many accounts and contacts you can reach.

Region

Company size

Buying role

Estimated segment✓ 99% SLA

4,003+Target accounts

18,020+Direct contacts

Decision-makers35%

Influencers45%

End users20%

Estimates from our current Noname Security API dataset. Exact counts come with your quote.

Reach the whole buying committee

A Noname Security API account is not one contact. We map the people who evaluate, buy, run and use it across API Security (Akamai).

Decision-makersC-suite & sponsors

CISOVP of EngineeringHead of Application SecurityCTO

Influencers & adminsEvaluate & configure

AppSec Engineering ManagerDevSecOps LeadPlatform Engineering LeadSecurity Champion Lead

End usersRun it every day

Software EngineersAppSec EngineersDevOps EngineersQA Engineers

These are examples. We build records for any department, seniority or custom title.

See exactly what you get

Every record carries 60+ fields, from verified email, direct dial and LinkedIn to full postal address, Noname Security API edition, coexisting stack and intent.

Contact	Buying role	Work email	Direct dial	Company phone	Fax	LinkedIn profile	Company	LinkedIn company page	Industry	Address 1	Address 2	City	State	ZIP code	Country	Noname Security API footprint	Intent	Status
SRSophia ReyesChief Information Security Officer (CISO)	Decision Maker	s.r***@apexc**.io	+1 (415) 55*-**	+1 (415) 55*-**	+1 (415) 55*-**	linkedin.com/in/s*ia-r*******	Apex Cloud Systems Inc.	linkedin.com/company/apex-cloud-sys	Enterprise Software & Cloud SaaS	100 Montgomery St	Ste 1800	San Francisco	CA	94104	United States	Noname Security API Enterprise Platform & Threat Defense	High	✓ Verified 2026
MWMarcus WebbLead Enterprise Security Architect	Influencer	m.w*@kensington*******.uk	+44 (20) 79*-**	+44 (20) 79*-**	+44 (20) 79*-**	linkedin.com/in/m*us-w*****	Kensington Global Capital Ltd	linkedin.com/company/kensington-capital	Financial Services & Investment Banking	25 Bank Street	Canary Wharf	London	Greater London	E14 5JP	United Kingdom	Noname Security API Cloud Architecture & Compliance	Medium	✓ Verified 2026
LFLena FischerSenior Security Operations (SecOps) Engineer	Practitioner	l.fi***@stackla****.de	+49 (89) 55*-**	+49 (89) 55*-**	+49 (89) 55*-**	linkedin.com/in/la-fi*******	StackLabs Cybersecurity GmbH	linkedin.com/company/sta***-cyber	Cloud Infrastructure & Cybersecurity Platforms	Leopoldstraße 180	—	Munich	Bavaria	80804	Germany	Noname Security API Continuous Protection Suite	High	✓ Verified 2026
JOJames O'ConnorVP of Information Security & Infrastructure	Decision Maker	j.oc**@veloce****.com	+1 (312) 55*-**	+1 (312) 55*-**	+1 (312) 55*-**	linkedin.com/in/j*s-oc******	Veloce Global Telecom Corp	linkedin.com/company/veloce-telecom	Telecommunications & Mobile Networks	233 S Wacker Dr	Ste 4200	Chicago	IL	60606	United States	Noname Security API Infrastructure Defense & Zero Trust	High	✓ Verified 2026
ALAstrid LindholmHead of Cyber Risk & Security Governance	Influencer	a.li**@nordi**.se	+46 (8) 55*-**	+46 (8) 55*-**	+46 (8) 55*-**	linkedin.com/in/a*id-li******	Nordic Payments & FinTech AB	linkedin.com/company/nordicpay-ab	Financial Technology & Digital Payments	Hamngatan 15	—	Stockholm	Stockholm County	111 47	Sweden	Noname Security API Enterprise Compliance Engine	Medium	✓ Verified 2026
DVDavid VanceChief Information Officer (CIO)	Decision Maker	d.va**@beacond****.com	+1 (703) 55*-**	+1 (703) 55*-**	+1 (703) 55*-**	linkedin.com/in/d*d-va******	Beacon Defense & Aerospace Inc.	linkedin.com/company/beacon-defense	Aerospace, Defense & Government Contracting	1850 Towers Crescent Plaza	—	Tysons	VA	22182	United States	Noname Security API FedRAMP Authorized Environment	High	✓ Verified 2026
RGRachel Green-CohenDirector of Enterprise Security Architecture	Influencer	r.co**@veritas****.org	+1 (617) 55*-**	+1 (617) 55*-**	+1 (617) 55*-**	linkedin.com/in/r*el-co******	Veritas Health System Inc.	linkedin.com/company/veritas-health-sys	Healthcare Networks & Hospital Systems	75 Francis St	—	Boston	MA	02115	United States	Noname Security API HIPAA Hardened Enforcement	Medium	✓ Verified 2026
YTYuri TanakaSecurity Operations & Threat Analyst	Practitioner	y.ta**@biosynth*****.jp	+81 (3) 55*-**	+81 (3) 55*-**	+81 (3) 55*-**	linkedin.com/in/yi-ta******	BioSynthetix Life Sciences KK	linkedin.com/company/biosynthetix-kk	Biotechnology & Pharmaceutical Research	Roppongi Hills Mori Tower	30F	Tokyo	Tokyo	106-6108	Japan	Noname Security API Threat Intelligence & Lifecycle Mgmt	Medium	✓ Verified 2026

Illustrative rows showing 20 of 60+ fields. Full records are unmasked.

We deliver 60+ data fields per record, including intent data. The sample shows a selection only. Tell us which fields you need, including any that aren't listed here, and we'll add them to your list.

Also available:Seniority & departmentJob functionTenure in roleEmployee countAnnual revenueSIC & NAICS codesParent companyWebsite & domainProduct editionContract & renewal timingIntent topics & scoreEmail verification date

How we prove an account runs Noname Security API

No scraped résumés or stale directories. Three layers confirm a live installation before a contact reaches your list. Read our verification protocol

Pillar 1 · Telemetry

Live DNS & script signals

We inspect response headers, DNS MX and CNAME records and live JavaScript bundles to confirm a running Noname Security API instance.

DNS · CNAME · MX recordsHTTP headers · JS bundles✓ Verified against live infrastructure

Pillar 2 · Operational intent

90-day hiring signals

We track job requisitions that ask for Noname Security API skills, which shows ongoing budget and headcount.

Now hiringNoname Security API Administrator

Now hiringNoname Security API Architect

Now hiringNoname Security API Engineer

Pillar 3 · Human & mailbox QA

Pre-delivery SMTP handshake

Each email is tested against the destination mail server, and titles are checked against current company rosters.

SMTP check ✓LinkedIn match ✓Title verified ✓

✓ Deliverable inbox and current role

Deliverability SLA

<3%

Maximum bounce rate, or we replace the contacts. Your sender reputation stays clean.

1:1 hard bounce replacement

Every email that hard-bounces within 30 days of delivery is replaced free, record for record.

24-hour pre-delivery ping

Live SMTP and MX checks right before we send your file.

Instant CRM import

Clean CSV or XLSX, ready for one-click import.

Ready for your outbound stack

Imports straight into the tools you use.

What are you trying to do?

Each campaign needs a different data strategy. Pick your goal to see how we build the audience.

Find companies on rival platforms and reach the people evaluating a move to, or away from, Noname Security API.

Conquesting playbook

Pitch integrations, add-ons and complementary tools to companies already running Noname Security API.

Ecosystem playbook

Build account lists around Noname Security API deployment scale and engage the full committee across departments.

ABM playbook

Conquesting audienceSample

Salt Security

Traceable

Wallarm

→

Noname Security API

Know the stack around every account

Noname Security API rarely runs alone. Every record is tagged with the tools detected alongside it, so you can segment by complementary stacks.

Akamai

AWS

Kong

Apigee

Jira

GitHub

Open the coexistence matrix

What Noname Security API customers look like

Anonymised profiles of companies in our Noname Security API dataset of 4,003+ accounts. Named accounts are shared in your free sample, never on a public page.

Noname Security API account profiles · anonymised

Company size	Industry	Country	Employees	Revenue
Mid-market	Banking & Fintech	Canada	200–999	$50M–$250M
Enterprise	Retail	Germany	5,000+	$1B+
Upper mid-market	Healthcare	United States	1,000–4,999	$250M–$1B
SMB	Telecommunications	Australia	50–199	$10M–$50M
Enterprise	Banking & Fintech	United States	10,000+	$5B+
Mid-market	Retail	United States	500–999	$100M–$250M
Mid-market	Healthcare	United Kingdom	200–999	$50M–$250M
Enterprise	Telecommunications	United States	5,000+	$1B+

Markets we cover

United States

India

United Kingdom

Canada

Germany

Australia

Singapore

France

New Zealand

Netherlands

Plus 170 more countries. Ask for a country-by-country count of Noname Security API accounts and we'll include it with your free sample.

Build the list your way

Every list is assembled from source to your product tier, job function, geography and revenue band. Nothing is a fixed export.

Editions & modules

Filter by what they actually run.

+Noname API Discovery+Noname Posture Management+Noname Runtime Protection+Noname Active Testing+Akamai API Security

Firmographics

Match revenue, size and industry.

+Industry+$1M–$10B+ revenue+Headcount+Ownership & funding+HQ & branches

Geography

Target any territory.

+US & Canada+US states+UK, DACH, Nordics+APAC & ANZ+Metro clusters

Need multi-attribute segments? Open the Audience Builder

What Noname Security API teams are struggling with

Know the friction before you reach out, and position your product where it matters.

Friction 1

Shadow and zombie APIs

ImpactUndocumented APIs leak data.

OpportunityOffer API inventory services.

Friction 2

Platform change after Akamai acquisition

ImpactCustomers review contracts and roadmap.

OpportunityTarget with API security alternatives.

Friction 3

Testing APIs before release

ImpactSecurity tests lag releases.

OpportunityPitch API testing services.

Intent triggers we track

✓API breach in sector

✓Open banking rollout

✓API gateway change

✓New AppSec leader

“Instead of waiting at a booth hoping for foot traffic, our reps arrived at the summit with a fully booked calendar of qualified buying committees. It transformed our event ROI.”

VP of Global Marketing, a cybersecurity vendorName withheld at the client's request

Read the 45 Briefings case study

Noname Security API list questions, answered

How many companies use Noname Security API?

Data InfoMetrix tracks 4,003 companies using Noname Security API, with 18,020 verified contacts at those accounts as of October 2026. The largest groups are Banking & Fintech, Retail and Healthcare. Counts are estimates from our database and market research, so ask us for a live count for your exact criteria.

Who buys and manages Noname Security API inside a company?

Noname Security API is usually owned by API Security (Akamai). Decision-makers include CISO, VP of Engineering and Head of Application Security; AppSec Engineering Manager and DevSecOps Lead shape the choice, and Software Engineers and AppSec Engineers use it day to day. Our Noname Security API list can include any of these roles.

Which Noname Security API products or editions can I target?

You can target accounts by the Noname Security API products they run, including Noname API Discovery, Noname Posture Management, Noname Runtime Protection, Noname Active Testing and Akamai API Security. Tell us which edition or module matters and we filter the list to those accounts.

What other software do Noname Security API customers use?

Noname Security API customers commonly also run Akamai, AWS, Kong, Apigee and Jira. Noname Security API is often connected to AWS API Gateway, so users of those tools overlap heavily. We can filter any list by this kind of stack overlap.

What are the main alternatives to Noname Security API?

The main alternatives to Noname Security API are Salt Security, Traceable and Wallarm. We also keep verified user lists for Salt Security, which is useful for competitive displacement campaigns.

When are Noname Security API customers most likely to buy?

Buying triggers we track for Noname Security API accounts include API breach in sector, open banking rollout, API gateway change and New AppSec leader. A common pain point is shadow and zombie APIs: Undocumented APIs leak data.

Can Data InfoMetrix deliver a free sample Noname Security contact list before ordering?

Yes. Data InfoMetrix delivers a complimentary 10-record sample tailored to your target Noname Security criteria—including target job titles, company size, and region—delivered within one business day with no obligation.

How does Data InfoMetrix guarantee email deliverability for Noname Security contacts?

Data InfoMetrix provides a 99% email deliverability guarantee on all Noname Security datasets. Every contact record undergoes real-time email verification within a 30 to 45-day refresh cycle, backed by a 1:1 hard bounce replacement policy for 30 days after delivery.

Sourcing and compliance. Business contacts come from public company sources, professional directories and opt-in publishing partners, then go through SMTP verification and human review. Lists are for B2B outreach: include an unsubscribe link and honour opt-outs (CAN-SPAM), and have a lawful basis such as legitimate interest when you email people in the EU or UK (GDPR). Read how we source and verify data