DNSBL Transparency
Fair warnings. Clear reasons. Time-limited enforcement. No drama.
What this is
bl.scott.ovh is a DNS-based blocklist used to reduce abuse against ScotNet services (mail, contact forms, web endpoints, and infrastructure). The goal is simple: keep services stable for legitimate users, and make automated abuse expensive.
This page explains the process and provides a self-check lookup. It does not publish a scrapeable “full list” of blocked IPs because that turns security telemetry into permanent internet litter.
Fair & just process
- Evidence-based: listings are triggered by security logs and threshold rules (not vibes).
- Proportional: temporary blocks are preferred; escalation happens only with repeated abuse.
- Explainable: reason codes describe what was observed.
- Reversible: listings expire or can be removed when the abuse stops and risk drops.
What gets listed
Listings are based on behaviour observed from a network address (an IP). Examples:
- Repeated authentication failures / brute force attempts
- Exploit scanning and known malicious probing patterns
- Contact form spam or automated submission attempts
- Mail abuse patterns (where applicable)
Listing lifecycle
Typical listings are temporary and expire automatically unless the behaviour repeats. Persistent abuse may extend a listing duration.
Reason codes
These are examples. The exact code may vary by subsystem.
| Code | Meaning |
|---|---|
WEB_BRUTEFORCE | Repeated auth failures or password guessing. |
WEB_EXPLOIT_SCAN | Exploit probes / known bad request patterns. |
FORM_SPAM | Automated form submissions, link spam, or bot behaviour. |
SMTP_AUTH_ABUSE | Abusive SMTP auth attempts (where applicable). |
MALICIOUS_BOT | High-confidence malicious automation. |
Self-check lookup
Enter an IPv4 or IPv6 address to see whether it is listed on bl.scott.ovh.
If a reason TXT is published for the entry, it will be shown.
Delisting
If you believe you were listed in error, you can request a review. Delisting decisions are based on the underlying evidence and whether the behaviour has stopped.
- Best fix: stop the abusive behaviour at the source (compromised host, misconfigured scanner, etc.).
- Then: use the DNSBL portal for guidance and delist options.
Privacy
This page discusses IP reputation in the context of security enforcement. For broader privacy principles across ScotNet services, see the main policy.
ScotNet privacy policy