Bug bounty program
MongoDB
Most upvoted reports0
No report of this program is publicly disclosed
Subdomains7,936
| Name | Scope | First seen |
|---|---|---|
| atlas-logs.cloud-stage.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| atlas-metrics.cloud-stage.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| atlas-pf-logs.cloud-stage.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| atlas-traces.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| atlas-cluster-ws.us-east-1.aws.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| atlas-cluster-ws.us-east-2.aws.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| cluster-connection.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| eu-west-1.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| pyroscope-atlas.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| wildcard.aws.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| wildcard.azure.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| wildcard.gcp.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| ws.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| wildcard.aws.ws.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| wildcard.azure.ws.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| wildcard.gcp.ws.services.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| us-east-1.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| atlas-logs.warpstream.cloud-stage.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| www.cloud-stage.mongodb.comstaging | In scope | 2026-11-14 |
| alertmanager-notifier.cloud-staging.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| atlas-logs.cloud-staging.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| otel-collector.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| pyroscope.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| global.gcp.services.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| slsbackup.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| alertmanager-notifier-0.us-east-1.cloud-staging.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| alertmanager-notifier-1.us-east-1.cloud-staging.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| alertmanager-notifier-0.us-east-2.cloud-staging.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| alertmanager-notifier-1.us-east-2.cloud-staging.mongodb.commonitoring, staging | In scope | 2026-11-14 |
| vminsert-az1.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| vminsert-az2.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| vmselect.cloud-staging.mongodb.comstaging | In scope | 2026-11-14 |
| alertmanager-notifier.cloud.mongodb.commonitoring | In scope | 2026-11-14 |
| amp.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-south-1.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-southeast-1.cloud.mongodb.com | In scope | 2026-11-14 |
| atlas-cluster-ws.cloud.mongodb.com | In scope | 2026-11-14 |
| atlas-gateway.cloud.mongodb.com | In scope | 2026-11-14 |
| atlas-logs.cloud.mongodb.commonitoring | In scope | 2026-11-14 |
| atlas-metrics.cloud.mongodb.commonitoring | In scope | 2026-11-14 |
| atlas-pf-logs.cloud.mongodb.commonitoring | In scope | 2026-11-14 |
| atlas-traces.cloud.mongodb.com | In scope | 2026-11-14 |
| global.lb-b-staging.ga.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| global.stitch-staging.ga.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| us-east-1.stitch-staging.ga.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| us-west-2.stitch-staging.ga.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| lb-b.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| lb-b-staging.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| eu-west-1.lb-a-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| us-east-1.lb-a-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| ap-northeast-1.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-south-1.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-southeast-1.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-southeast-2.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-central-1.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-west-2.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| sa-east-1.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-1.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-west-2.lb-a.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-1.lb-b-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| us-west-2.lb-b-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| ap-south-1.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-southeast-1.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| ap-southeast-2.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-central-1.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-west-1.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-west-2.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| sa-east-1.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-1.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-2.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-west-2.lb-b.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-central-1.lb-d.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-west-2.lb-d.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-1.lb-d.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-west-2.lb-d.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-1.lb-e-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| use1-az1.us-east-1.lb-e-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| use1-az2.us-east-1.lb-e-staging.r53.aws.cloud.mongodb.comstaging | In scope | 2026-11-14 |
| ap-southeast-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| apse2-az1.ap-southeast-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| apse2-az2.ap-southeast-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| apse2-az3.ap-southeast-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-central-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euc1-az1.eu-central-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euc1-az2.eu-central-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euc1-az3.eu-central-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-west-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euw1-az1.eu-west-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euw1-az2.eu-west-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euw1-az3.eu-west-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| eu-west-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euw2-az2.eu-west-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| euw2-az3.eu-west-2.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| us-east-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| use1-az1.us-east-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| use1-az2.us-east-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| use1-az4.us-east-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| use1-az5.us-east-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
| use1-az6.us-east-1.lb-e.r53.aws.cloud.mongodb.com | In scope | 2026-11-14 |
7,936 names are covered by the program's own scope; 9 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.