Skip to content

Dutch Government Bugbounty scope, subdomains and endpoints

Notifications You must be signed in to change notification settings

zzzteph/Dutch_Gov_Scope

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10,075 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Dutch Government Bug Bounty Scope

Welcome to the repository dedicated to collecting and maintaining a precise list of the Dutch government's bug bounty scope. This includes domains, subdomains, and endpoints (URLs).
This is NOT an official bug bounty scope.

To report a vulnerability or to learn more about Coordinated Vulnerability Disclosure (CVD), visit:
👉 https://www.ncsc.nl/contact/kwetsbaarheid-melden

Overview

This project aims to provide the most accurate and detailed list of domains and endpoints that are in scope of the Dutch government’s bug bounty program. By mapping and monitoring relevant infrastructure, the goal is to support the security and visibility of government digital assets.

What is in scope?

This repository focuses on verified, government-related resources. The scope list is built to ensure it is the most accurate list available.

Each resource is included only if it meets the following criteria:

  1. Meta tag: The page must include the RIJKSOVERHEID.Organisatie meta information.
  2. Official logo: The site must display the Dutch government logo.
  3. Clear affiliation: There must be a clear mention of the official government body or agency.

How It Works

The data is collected using a semi-automated pipeline and updated regularly. All analysis is done via Github actions and results are stored and synced in the scan_scope.db SQLite database. The process includes:

  1. Manual updates: Input resources are stored in the /scope folder.
  2. Weekly sync with CommunicatieRijk data.
  3. Automated collection per domain:
    • Subdomain discovery: Using Amass, Subfinder, and DNSX for validation.
    • Endpoint discovery: HTTPX filters and confirms valid HTTP/HTTPS endpoints.

Repository Structure

Scanning examples

curl --silent https://raw.githubusercontent.com/zzzteph/DutchGovScope/refs/heads/main/storage/rijksoverheid/endpoints.txt | ./nuclei -silent -id geoserver-login-panel
curl --silent https://raw.githubusercontent.com/zzzteph/DutchGovScope/refs/heads/main/storage/rijksoverheid/endpoints.txt | ./nuclei -silent -id exposure -severity critical,high

Scanning via Docker

curl --silent https://raw.githubusercontent.com/zzzteph/DutchGovScope/refs/heads/main/storage/rijksoverheid/endpoints.txt -o endpoints.txt | docker run -v "$PWD:/data" --rm projectdiscovery/nuclei -silent -id geoserver-login-panel
curl --silent https://raw.githubusercontent.com/zzzteph/DutchGovScope/refs/heads/main/storage/rijksoverheid/endpoints.txt -o endpoints.txt | docker run -v "$PWD:/data" --rm projectdiscovery/nuclei -silent -id exposure -severity critical,high

Links and Acknowledgements


To report a vulnerability or learn more, please visit:
👉 https://www.ncsc.nl/contact/kwetsbaarheid-melden

About

Dutch Government Bugbounty scope, subdomains and endpoints

Topics

Resources

Stars

Watchers

Forks

Sponsor this project

  •  

Contributors 2

  •  
  •  

Languages