Postmaster / Technical Contact

This page provides contact information for reporting technical issues, abuse, or problems related to email, DNS, or server operations for this domain.

netraam.net is a privately run, non-commercial infrastructure. It is maintained by one person on a best-effort basis.

Contact Addresses

• Abuse reports: abuse@netraam.net
• Postmaster and security reports: postmaster@netraam.net

Reports in English or Dutch are welcome.

What You Can Report

• Email delivery issues (bounces, blocks, greylisting)
• SPF/DKIM/DMARC-related problems
• Abuse incidents (spam, spoofing attempts, brute-force activity)
• DNS issues involving this domain
• Security vulnerabilities or incidents

Reporting a Security Vulnerability

If you believe you have found a security vulnerability, please send the full details straight to postmaster@netraam.net. There is no need to ask first which channel to use: this is it.

A useful report includes:

• the affected host name, URL or service
• a description of the issue and its practical impact
• the steps needed to reproduce it
• the date and time of your testing, and the IP address you tested from

No PGP key is published for this address. Please keep the report to what is needed to understand and reproduce the issue, and do not include any personal data or credentials you may have come across.

No bug bounty

There is no bug bounty programme, and no payment or other reward is offered for any report. Requests for payment, whether before or after disclosure, will not be answered. Reports are still appreciated, and genuine findings will be fixed and, if you wish, acknowledged.

Out of scope

The following are not considered vulnerabilities unless accompanied by a working proof of concept that shows real impact:

• Output from automated scanners
• Missing or “weak” HTTP security headers, cookie flags or clickjacking protection on pages without sensitive actions
• Choices of SPF, DKIM or DMARC policy
• Disclosure of software names or version numbers
• TLS configuration preferences (supported protocols, cipher order)
• Missing rate limiting
• Self-XSS, logout CSRF, and similar low-impact issues

Ground rules for testing

• Do not run denial-of-service tests or high-volume scans.
• Do not access, modify or delete data that is not yours.
• Do not test via social engineering or physical access.
• Give a reasonable amount of time to fix an issue before you disclose it publicly.

Security Policy

This domain follows the RFC 9116 security.txt standard. You can find the official security metadata here:

/.well-known/security.txt

Server Notes

These servers are actively maintained. DNSSEC, SPF, DKIM and DMARC are enabled and monitored for secure and reliable operations.

Last updated: October 2026