Skip to content

zzzteph/Dutch_Gov_Scope

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

10,454 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 and subdomains.
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 subdomains 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. Each domain is included only after passing a multi-tier verification pipeline:

  1. HTTP + SSL signals: Meta tags (overheid:authority, rijksoverheid.org), legal accessibility statements (toegankelijkheidsverklaring.nl), government analytics infrastructure, SSL certificate organisation field.
  2. Rendered DOM check: Browser-rendered page (Playwright) to catch SPAs — same signal checks after JavaScript executes.
  3. Visual identity check: Claude vision on a page screenshot — confirms the standard Rijksoverheid header (dark navy bar, Dutch coat of arms, pink stripe) or equivalent agency branding as the site's own identity.

How It Works

All analysis runs via GitHub Actions. Results are stored as plain text files in the repository.

  1. Domain scope maintenanceengine/refresh_rijksoverheid.py:

    • Monthly sync with the official CommunicatieRijk websiteregister
    • New domains are verified through the three-tier pipeline (engine/verify_rijksoverheid.py)
    • Confirmed domains → scope/rijksoverheid.txt; rejected/uncertain → scope/rijksoverheid_invalid.txt
  2. Subdomain discovery — runs daily via GitHub Actions:

    • Subfinder with inline DNS validation (-active) on a rotating 3% slice of scope (with overlap)
    • Results merged into per-domain storage files and aggregated

Repository Structure

Scanning examples

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

Scanning via Docker

curl --silent https://raw.githubusercontent.com/zzzteph/DutchGovScope/refs/heads/main/storage/rijksoverheid/subdomains.txt -o subdomains.txt && docker run -v "$PWD:/data" --rm projectdiscovery/nuclei -silent -id geoserver-login-panel -l /data/subdomains.txt

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

Languages