- Top reward
- No cash rewards
- Top severity paid
- Critical
- Assets in scope
- 24
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report by email
- [email protected]
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 3 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What HackerOne lists as the payout for each severity.
This program does not pay cash rewards.
- Response
-
Within 3 days
Within 3 business days, we will acknowledge that your report has been received.
- Safe harbor
-
Full
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Department of State will not recommend or pursue legal action related to your research.
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
24 assets you may test.
Wildcard domains 21
- *.america.gov Critical No bounty
- *.devtestfan1.gov Critical No bounty
- *.elguardia.net Critical No bounty
- *.fan.gov Critical No bounty
- *.fsgb.gov Critical No bounty
- *.iawg.gov Critical No bounty
- *.ibwc.gov Critical No bounty
- *.osac.gov Critical No bounty
- *.pepfar.gov Critical No bounty
- *.preprodfan.gov Critical No bounty
- *.rewardsforjustice.net Critical No bounty
- *.securitytestfan.gov Critical No bounty
- *.state.gov Critical No bounty
- *.supportfan.gov Critical No bounty
- *.usconsulate.gov Critical No bounty
- *.usdoscloud.gov Critical No bounty
- *.usembassy.gov Critical No bounty
- *.usmission.gov Critical No bounty
- *.ustraveldocs.com Critical No bounty
- *.usvisaappt.com Critical No bounty
- *.usvisascheduling.com Critical No bounty
Web 2
- https://ais.usvisa-info.com Critical No bounty
- https://casadmin.peckham.org Critical No bounty
Source code 1
- https://github.com/USStateDept Critical No bounty
Rules
What the policy asks of you, and the bug types it won't reward, quoted from U.S. Department of State (via HackerOne)'s policy. "We" in these lines means the program, not this site.
While testing
-
Notify us as soon as possible after you discover a real or potential security issue.
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
-
Provide us a reasonable amount of time (typically 100 calendar days) to resolve the issue before coordinated disclosure.
-
Do not submit a high volume of low-quality reports.
-
Network denial or distributed denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
-
Physical testing (e.g., office access, open doors, tailgating), social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing
-
Using `-risk=3` is explicilty prohibited if using `sqlmap`.
-
Archiving subdomain takeover proofs-of-concept on archive.org, or any similar archiving site, is strictly prohibited.
Not accepted
-
Clickjacking on pages with no sensitive actions
-
Archived GitHub repos are out of scope
-
Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
-
Attacks requiring MITM or physical access to a user's device.
-
Previously known vulnerable libraries without a working Proof of Concept.
-
Comma Separated Values (CSV) injection without demonstrating a vulnerability.
-
Missing best practices in SSL/TLS configuration.
-
Any activity that could lead to the disruption of our service (DoS).
-
Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
-
Rate limiting or brute force issues on non-authentication endpoints
-
Missing best practices in Content Security Policy.
-
Missing HTTP Only or Secure flags on cookies
-
Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
-
Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
-
Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
-
Tab nabbing
-
Open redirect - unless an additional security impact can be demonstrated
-
Issues that require unlikely user interaction
-
User enumeration, unless you can demonstrate that a brute force attack is likely to succeed.
-
Social engineering (e.g. phishing, vishing, smishing)
Summarised with AI from the program policy on HackerOne, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from hackerone.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Introduction
The Department of State (DOS) is committed to ensuring the security of the American public by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.
We encourage you to contact us to report potential vulnerabilities in our systems in accordance with this policy.
Authorization
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Department of State will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known to such third party.
Guidelines
Under this policy, “research” means activities in which you:
- Notify us as soon as possible after you discover a real or potential security issue.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
- Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.
- Provide us a reasonable amount of time (typically 100 calendar days) to resolve the issue before coordinated disclosure.
- Do not submit a high volume of low-quality reports.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including Personally Identifiable Information (PII), medical information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
Test Methods
In addition to any proscriptions in the guidelines above, the following test methods are NOT authorized:
- Network denial or distributed denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
- Physical testing (e.g., office access, open doors, tailgating), social engineering (e.g., phishing, vishing), or any other non-technical vulnerability testing
• Using
-risk=3is explicilty prohibited if usingsqlmap.
Scope
This policy applies to all Department internet accessible systems and services to include those in the Scope section.
Vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us at [email protected] before starting your research (or at the security contact for the system’s domain name listed in the .gov WHOIS).
We ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.
Out-Of-Scope
• Clickjacking on pages with no sensitive actions
• Archived GitHub repos are out of scope
• Archiving subdomain takeover proofs-of-concept on archive.org, or any similar archiving site, is strictly prohibited. This constitutes an unauthorized public disclosure
• Many sites share the same code base - please see the table below
• If a second researcher submits an already reported vulnerability against any of the sites in the table below, they will be closed as Duplicate
• If the same researcher submits duplicate reports against two or more of the sites in the table below, only the first will be accepted and the remaining will be closed as N/A
• Cross-Site Request Forgery (CSRF) on unauthenticated forms or forms with no sensitive actions
• Attacks requiring MITM or physical access to a user's device.
• Previously known vulnerable libraries without a working Proof of Concept.
• Comma Separated Values (CSV) injection without demonstrating a vulnerability.
• Missing best practices in SSL/TLS configuration.
• Any activity that could lead to the disruption of our service (DoS).
• Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS
• Rate limiting or brute force issues on non-authentication endpoints
• Missing best practices in Content Security Policy.
• Missing HTTP Only or Secure flags on cookies
• Missing email best practices (Invalid, incomplete or missing SPF/DKIM/DMARC records, etc.)
• Vulnerabilities only affecting users of outdated or unpatched browsers [Less than 2 stable versions behind the latest released stable version]
• Software version disclosure / Banner identification issues / Descriptive error messages or headers (e.g. stack traces, application or server errors).
• Tab nabbing
• Open redirect - unless an additional security impact can be demonstrated
• Issues that require unlikely user interaction
• User enumeration, unless you can demonstrate that a brute force attack is likely to succeed.
• Social engineering (e.g. phishing, vishing, smishing)
| Sites Sharing the Same Codebase (MWP) | |---|---|---|---| |ae.usembassy.gov| er.usembassy.gov| lv.usembassy.gov| share.america.gov| |af.usembassy.gov| es.usembassy.gov| ly.usembassy.gov| si.usembassy.gov| |al.usembassy.gov| et.usembassy.gov| ma.usembassy.gov| sk.usembassy.gov| |am.usembassy.gov| fi.usembassy.gov| md.usembassy.gov| sl.usembassy.gov| |ao.usembassy.gov| fj.usembassy.gov| me.usembassy.gov| sm.usmission.gov| |ar.usembassy.gov| fm.usembassy.gov| mepi.state.gov| sn.usembassy.gov| |asean.usmission.gov| fr.usembassy.gov| mg.usembassy.gov| so.usembassy.gov| |at.usembassy.gov| ga.usembassy.gov| mh.usembassy.gov| spanmag.state.gov| |au.usembassy.gov| ge.usembassy.gov| mk.usembassy.gov| sr.usembassy.gov| |az.usembassy.gov| geneva.usmission.gov| ml.usembassy.gov| ss.usembassy.gov| |ba.usembassy.gov| gh.usembassy.gov| mm.usembassy.gov| sv.usembassy.gov| |bb.usembassy.gov| gm.usembassy.gov| mn.usembassy.gov| sy.usembassy.gov| |bd.usembassy.gov| gn.usembassy.gov| mr.usembassy.gov| sz.usembassy.gov| |be.usembassy.gov| gq.usembassy.gov| mt.usembassy.gov| td.usembassy.gov| |bf.usembassy.gov| gr.usembassy.gov| mu.usembassy.gov| tg.usembassy.gov| |bg.usembassy.gov| gt.usembassy.gov| mw.usembassy.gov| th.usembassy.gov| |bh.usembassy.gov| gw.usmission.gov| mx.usembassy.gov| tj.usembassy.gov| |bi.usembassy.gov| gy.usembassy.gov| my.usembassy.gov| tl.usembassy.gov| |bj.usembassy.gov| hk.usconsulate.gov| mz.usembassy.gov| tm.usembassy.gov| |bm.usconsulate.gov| hn.usembassy.gov| na.usembassy.gov| tn.usembassy.gov| |bn.usembassy.gov| hr.usembassy.gov| nato.usmission.gov| tr.usembassy.gov| |bo.usembassy.gov| ht.usembassy.gov| ne.usembassy.gov| tt.usembassy.gov| |br.usembassy.gov| hu.usembassy.gov| ng.usembassy.gov| tz.usembassy.gov| |bs.usembassy.gov| icao.usmission.gov| ni.usembassy.gov| ua.usembassy.gov| |bw.usembassy.gov| id.usembassy.gov| nl.usembassy.gov| ug.usembassy.gov| |by.usembassy.gov| ie.usembassy.gov| no.usembassy.gov| uk.usembassy.gov| |bz.usembassy.gov| il.usembassy.gov| np.usembassy.gov| usau.usmission.gov| |ca.usembassy.gov| in.usembassy.gov| nz.usembassy.gov| usembassy.gov| |cd.usembassy.gov| iq.usembassy.gov| om.usembassy.gov| useu.usmission.gov| |cf.usembassy.gov| ir.usembassy.gov| osce.usmission.gov| usoas.usmission.gov| |cg.usembassy.gov| is.usembassy.gov| pa.usembassy.gov| usoecd.usmission.gov| |ch.usembassy.gov| it.usembassy.gov| pe.usembassy.gov| usun.usmission.gov| |ci.usembassy.gov| jm.usembassy.gov| pg.usembassy.gov| usunrome.usmission.gov| |cl.usembassy.gov| jmh.usembassy.gov| ph.usembassy.gov| uy.usembassy.gov| |cm.usembassy.gov| jo.usembassy.gov| pk.usembassy.gov| uz.usembassy.gov| |co.usembassy.gov| jp.usembassy.gov| pl.usembassy.gov| va.usembassy.gov| |cr.usembassy.gov| ke.usembassy.gov| pt.usembassy.gov| ve.usembassy.gov| |cu.usembassy.gov| kg.usembassy.gov| pw.usembassy.gov| vienna.usmission.gov| |cv.usembassy.gov| kh.usembassy.gov| py.usembassy.gov| vn.usembassy.gov| |cw.usconsulate.gov| km.usembassy.gov| qa.usembassy.gov| ws.usembassy.gov| |cy.usembassy.gov| kr.usembassy.gov| ro.usembassy.gov| xk.usembassy.gov| |cz.usembassy.gov| kw.usembassy.gov| rs.usembassy.gov| yali.state.gov| |de.usembassy.gov| kz.usembassy.gov| ru.usembassy.gov| ye.usembassy.gov| |dj.usembassy.gov| la.usembassy.gov| rw.usembassy.gov| ylai.state.gov| |dk.usembassy.gov| lb.usembassy.gov| sa.usembassy.gov| za.usembassy.gov| |do.usembassy.gov| lk.usembassy.gov| sb.usembassy.gov| zm.usembassy.gov| |dz.usembassy.gov| lr.usembassy.gov| sc.usembassy.gov| zw.usembassy.gov| |ec.usembassy.gov| ls.usembassy.gov| sd.usembassy.gov| |ee.usembassy.gov| lt.usembassy.gov| se.usembassy.gov| |eg.usembassy.gov| lu.usembassy.gov| sg.usembassy.gov|
Reporting a Vulnerability
Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely the Department of State, we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process (https://www.cisa.gov/coordinated-vulnerability-disclosure-process). We may also share your report with other U.S. Government entities if required by law or regulation. We will not share your name or contact information without express permission.
What we would like to see from you
In order to help us triage and prioritize submissions, we recommend that your reports:
- Describe when the vulnerability was discovered, its location, and the potential impact of exploitation.
- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots (if they don’t contain sensitive data) are helpful).
- Provide a mitigation recommendation and include any related technical information.
- Be in English, if possible.
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
- Within 3 business days, we will acknowledge that your report has been received.
- To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
- We will maintain an open dialogue to discuss issues.
Questions
Questions regarding this policy may be sent to [email protected]. We also invite you to contact us with suggestions for improving this policy.
#Legal This policy does not authorize, give permission, or otherwise allow express or implied access to DOS information systems to any individual, group of individuals, consortium, partnership, or any other business or legal entity. However, if a security researcher working in accordance with the terms and conditions of this VDP program discloses a vulnerability, then: (1) DOS will, in the exercise of its authorities, take the following steps to: (1) not initiate or recommend any law enforcement action or civil actions related to such activities against that researcher, and (2) if required, inform the pertinent law enforcement agencies or civil plaintiffs that researcher activities were, to the best of our knowledge, conducted pursuant to, and in compliance, with the terms and conditions of the program.
You must otherwise comply with all applicable Federal, State, and local laws in connection with your security research activities. You may not engage in any security research or vulnerability disclosure activity that is inconsistent with terms and conditions of the program or the law. If you engage in any activities that are inconsistent with the terms and conditions of the program or the law, you will not be considered a security researcher and may be subject to criminal penalties and civil liability.
To the extent that any security research or vulnerability disclosure activity involves the networks, systems, information, applications, products, or services of a non-DOS entity (e.g., other Federal departments or agencies; State, local, or tribal governments; private sector companies or persons; employees or personnel of any such entities; or any other such third party), that non-DOS entity may independently determine whether to pursue legal action or remedies related to such activities.
DOS may modify the terms and conditions or terminate the program at any time.