Skip to content

Bug bounty program

Platform
Bugcrowd
Bounties
Pays
Assets in scope
11
Disclosed reports
0
Subdomains
11,675
Vendor on CyberSIXT
Tesla (26 CVEs, 0 exploited)

Most upvoted reports0

No report of this program is publicly disclosed

Subdomains11,675

Subdomains of Tesla
NameScopeFirst seen
ftp.solarcity.comdataIn scope2026-11-14
athena-stage-db.scfs.solarcity.comdata, stagingIn scope2026-11-14
backup-vpn.scfs.solarcity.comdata, vpnIn scope2026-11-14
development-db-01.scfs.solarcity.comdata, devIn scope2026-11-14
infra-redis-01.scfs.solarcity.comdataIn scope2026-11-14
pre-athena-db-01.scfs.solarcity.comdataIn scope2026-11-14
prerelease-db-01.scfs.solarcity.comdata, stagingIn scope2026-11-14
prod-db-01.scfs.solarcity.comdataIn scope2026-11-14
prod-db-02.scfs.solarcity.comdataIn scope2026-11-14
prod-db-helios.scfs.solarcity.comdataIn scope2026-11-14
prod-helios-db-01.scfs.solarcity.comdataIn scope2026-11-14
prod-helios-db-02.scfs.solarcity.comdataIn scope2026-11-14
reporting-athena-db-01.scfs.solarcity.comdataIn scope2026-11-14
reporting-db-01.scfs.solarcity.comdataIn scope2026-11-14
reporting-db-01-old.scfs.solarcity.comdata, legacyIn scope2026-11-14
stage-db-01.scfs.solarcity.comdata, stagingIn scope2026-11-14
vault-db.scfs.solarcity.comdata, toolsIn scope2026-11-14
rabbitmq-test-03.dev.scsg.solarcity.comdata, dev, testIn scope2026-11-14
sftp.solarcity.comdataIn scope2026-11-14
sftp2.solarcity.comdataIn scope2026-11-14
tclips-db-prod-cn-north-1.staging.ap.cloud.tesla.cndata, stagingIn scope2026-11-14
tclips-db-prod-cn-north-1.ap.cloud.tesla.cndataIn scope2026-11-14
vehicle-files.eng.cnn1.vn.cloud.tesla.cndataIn scope2026-11-14
vehicle-files.prd.cnn1.vn.cloud.tesla.cndataIn scope2026-11-14
vehicle-files.eng.vn.cloud.tesla.cndataIn scope2026-11-14
vehicle-files.prd.vn.cloud.tesla.cndataIn scope2026-11-14
s3.a.pvg61.tcs.tesla.cndataIn scope2026-11-14
s3.a.energy.pvg61.tcs.tesla.cndataIn scope2026-11-14
s3.a.fleet.pvg61.tcs.tesla.cndataIn scope2026-11-14
s3.pvg61.tcs.tesla.cndataIn scope2026-11-14
s3.a.pvg62.tcs.tesla.cndataIn scope2026-11-14
s3.a.energy.pvg62.tcs.tesla.cndataIn scope2026-11-14
s3.a.fleet.pvg62.tcs.tesla.cndataIn scope2026-11-14
s3.pvg62.tcs.tesla.cndataIn scope2026-11-14
s3.a.vast.tesla-hermes-snapshot-motors.tcs.tesla.cndataIn scope2026-11-14
s3.a.vast.tcs.tesla.cndataIn scope2026-11-14
s3.b.vast.tcs.tesla.cndataIn scope2026-11-14
s3.a.energy.vast.tcs.tesla.cndataIn scope2026-11-14
s3.b.energy.vast.tcs.tesla.cndataIn scope2026-11-14
s3.a.fleet.vast.tcs.tesla.cndataIn scope2026-11-14
vehicle-files.tesla.cndataIn scope2026-11-14
ftp.akamai-apigateway-vfx.tesla.comapi, dataIn scope2026-11-14
upload.apigateway-logging.tesla.comapi, data, monitoringIn scope2026-11-14
vehicle-files.eng.vn.cloud.tesla.comdataIn scope2026-11-14
s3.hermes-stream-api.prd.eu.vn.cloud.tesla.comapi, dataIn scope2026-11-14
s3.eu.vn.cloud.tesla.comdataIn scope2026-11-14
vehicle-files.eng.euw1.vn.cloud.tesla.comdataIn scope2026-11-14
vehicle-files.prd.euw1.vn.cloud.tesla.comdataIn scope2026-11-14
s3.eng.na.vn.cloud.tesla.comdataIn scope2026-11-14
tesla-hermes-snapshot-motors-eng.s3.eng.na.vn.cloud.tesla.comdataIn scope2026-11-14
files.hermes-stream-api.prd.na.vn.cloud.tesla.comapi, dataIn scope2026-11-14
s3.prd.na.vn.cloud.tesla.comdataIn scope2026-11-14
tesla-hermes-snapshot-motors.s3.prd.na.vn.cloud.tesla.comdataIn scope2026-11-14
files.hermes-ap.prd.vn.cloud.tesla.comdataIn scope2026-11-14
vehicle-files.prd.vn.cloud.tesla.comdataIn scope2026-11-14
vehicle-files.eng.usw2.vn.cloud.tesla.comdataIn scope2026-11-14
upload.assistant-api.prd.usw2.vn.cloud.tesla.comapi, dataIn scope2026-11-14
vehicle-files.prd.usw2.vn.cloud.tesla.comdataIn scope2026-11-14
upload.digitalassets.tesla.comdataIn scope2026-11-14
uploads.extgithub.tesla.comdataIn scope2026-11-14
ftp.extsentry.tesla.comdataIn scope2026-11-14
files-ownership.tesla.comdataIn scope2026-11-14
files-ownership-stage.tesla.comdata, stagingIn scope2026-11-14
fleet-api-files-prd.tesla.comapi, dataIn scope2026-11-14
uploads.github-ap.tesla.comdata, gitIn scope2026-11-14
uploads.github-fw.tesla.comdata, gitIn scope2026-11-14
uploads.github-it.tesla.comdata, gitIn scope2026-11-14
s3-sidekick-ssl.github.tesla.comdata, gitIn scope2026-11-14
uploads.github.tesla.comdata, gitIn scope2026-11-14
s3.energy.obs.tesla.comdataIn scope2026-11-14
s3.b.ams15.tcs.tesla.comdataIn scope2026-11-14
s3.b.energy.ams15.tcs.tesla.comdataIn scope2026-11-14
s3.b.ams17.tcs.tesla.comdataIn scope2026-11-14
s3.b.energy.ams17.tcs.tesla.comdataIn scope2026-11-14
s3.a.buf01.tcs.tesla.comdataIn scope2026-11-14
s3.a.iad06.tcs.tesla.comdataIn scope2026-11-14
s3.a.smf11.tcs.tesla.comdataIn scope2026-11-14
s3.b.smf11.tcs.tesla.comdataIn scope2026-11-14
s3.c.smf11.tcs.tesla.comdataIn scope2026-11-14
s3.d.smf11.tcs.tesla.comdataIn scope2026-11-14
s3.a.smf12.tcs.tesla.comdataIn scope2026-11-14
s3.a.energy.smf12.tcs.tesla.comdataIn scope2026-11-14
s3.a.smf13.tcs.tesla.comdataIn scope2026-11-14
s3.a.energy.smf13.tcs.tesla.comdataIn scope2026-11-14
s3.a.vast.tesla-hermes-snapshot-motors.tcs.tesla.comdataIn scope2026-11-14
s3.a.vast-dr.tcs.tesla.comdataIn scope2026-11-14
s3.a.vast.tcs.tesla.comdataIn scope2026-11-14
s3.b.vast.tcs.tesla.comdataIn scope2026-11-14
s3.a.energy.vast.tcs.tesla.comdataIn scope2026-11-14
s3.b.energy.vast.tcs.tesla.comdataIn scope2026-11-14
tesla-hermes-snapshot-eng-eu.s3.ap.tesla.servicesdataIn scope2026-11-14
tesla-hermes-snapshot-eu.s3.ap.tesla.servicesdataIn scope2026-11-14
backup.tesla.servicesdataIn scope2026-11-14
db.tesla.servicesdataIn scope2026-11-14
redis-sca-dev.mwww.antivirus.www-dev.admin.alumni.dev.tesla.servicesadmin, data, devIn scope2026-11-14
files.tesla.servicesdataIn scope2026-11-14
files1.tesla.servicesdataIn scope2026-11-14
ftp.tesla.servicesdataIn scope2026-11-14
ftp1.tesla.servicesdataIn scope2026-11-14
ftp2.tesla.servicesdataIn scope2026-11-14

11,661 names are covered by the program's own scope; 0 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.

A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.