National Day Calendar
Vulnerability disclosure program on security.txt nationaldaycalendar.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 1
- 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 the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
National Day Calendar does not operate a paid bug bounty program at this time. We do not offer financial rewards for vulnerability reports.
- Response
-
Within 3 days
Response time: 3 business days
- Safe harbor
-
Full
Legal Protection: We will not pursue legal action against you.
- Hall of fame
-
Yes
We will offer you a spot in our Security Acknowledgments Hall of Fame once the issue is resolved.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
1 asset you may test.
Domains 1
- nationaldaycalendar.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from National Day Calendar's policy. "We" in these lines means the program, not this site.
While testing
-
Report Privately: Share the full details of any found vulnerability exclusively with us by emailing the address on the policy page .
-
Provide Details: Include a clear, written description of the vulnerability and the steps needed to reproduce it (a "Proof of Concept").
-
Do No Harm: Do not attempt to access, modify, or delete data belonging to our users. Do not perform Denial of Service (DoS) attacks or use social engineering against our staff.
-
Allow Time: Give us a reasonable amount of time to investigate and remediate the issue before making any information public.
Not accepted
-
"Clickjacking" on pages without sensitive actions
-
Lack of "Best Practice" headers (e.g., CSP, HSTS) unless a bypass is demonstrated
-
Reports of non-masked passwords in UI
-
Spam or Social Engineering techniques
-
Publicly disclosed vulnerabilities in third-party services
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 12 Nov 2026. Last checked 3 hours 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.