Skip to content

SURF

Bug bounty on security.txt surf.nl

Accepting reports security.txt
Top reward
Not published
Top severity paid
Not published
Assets in scope
2
Public CVEs
0
Last change
No changes yet

At a glance

What to know before you start testing.

Pays cash
Amounts are not published; ask before you invest time.
Report by email
[email protected]
Partial safe harbor
Some legal protection; read the terms.
Replies within 5 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.

The policy page has no reward table. Here is what it says, in its own words.

Pays cash
Yes We may give you a reward for your research but are not obliged to do so.
Response
Within 5 days We will respond to your report within 5 business days with our evaluation of the report and an expected resolution date.
Safe harbor
Partial If you follow the conditions given in this agreement, we will not take legal action against you. However, the Public Prosecutor always has the right to decide whether or not to prosecute you.
Hall of fame
Yes If you wish, we will mention your name as a vulnerability discoverer in the weakness report.

Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

2 assets you may test.

Domains 2

  • surfnet.nl
  • surf.nl

Rules

What the policy asks of you, and the bug types it won't reward, quoted from SURF's policy. "We" in these lines means the program, not this site.

While testing

  • Do not abuse the found vulnerability, for example: downloading more data than necessary
  • Do not share the vulnerability with others until it is resolved
  • Do not test the physical security or third-party application, social engineering techniques (distributed) denial-of-service, malware, or spam.
  • Encrypt your findings with our PGP key to prevent the information from falling into the wrong hands.
  • Be extra cautious with personal data

Not accepted

  • HTTP 404 codes/pages or other HTTP non-200 codes/pages and Content Spoofing/Text Injection on these pages.
  • fingerprint version banner disclosure on common/public services.
  • disclosure of known public files or directories or non-sensitive information, (e.g. robots.txt).
  • clickjacking and issues only exploitable through clickjacking.
  • lack of Secure/HTTPOnly flags on non-sensitive Cookies.
  • OPTIONS HTTP method enabled.
  • anything related to HTTP security headers
  • SSL Configuration Issues
  • SPF, DKIM, DMARC issues.
  • host header injection.
  • reporting older versions of any software without proof of concept or working exploit.
  • information leakage in metadata.

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 11 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.

Search NVD

No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.