🔍 OSINT Reconnaissance Changedetection.io Processor Agent
Comprehensive network intelligence and security monitoring leveraging changedetection.io
This is a processor agent plugin for changedetection.io change detection and notification dashboard.
Monitor your infrastructure for unexpected changes. Detect unauthorized modifications to SSL/TLS certificates, DNS records, BGP routing, open ports, WHOIS registration details, HTTP security headers, and TLS cipher configurations. Perfect for security teams, DevOps engineers, SRE teams, and OSINT practitioners who need continuous visibility into their infrastructure's security posture. Get instant notifications when certificates are about to expire, DNS records change, new vulnerabilities appear, or network paths are rerouted—before they become security incidents or outages.
Use the existing text filters built into changedetection.io to trim out information you don't need and keep only what's relevant to you. Easily connect change alerts to Discord, Slack, email, and 90+ other notification backends, leveraging the awesomeness of changedetection.io's powerful notification system.
- Create a watch with URL:
https://example.com - Select processor: OSINT Reconnaissance
Then see your full OSINT report as a text change which can be easily connected to Discord, email, ntfy, matrix, ms-teams, slack and 90+ other notifications.
✨ Features
Network Intelligence
- DNS Records (A, AAAA, MX, NS, TXT, SOA, CAA)
- DNSSEC Validation (cryptographic signatures, chain of trust)
- WHOIS Lookup (registration, nameservers, expiry)
- BGP/ASN Info (ISP, network ownership)
- Traceroute (network path analysis)
- MAC Address (vendor identification via IEEE OUI)
Email Security
- SPF Records (Sender Policy Framework anti-spoofing)
- DMARC Records (email authentication policy)
- DKIM Records (email signature verification)
- Email security posture assessment
Security Analysis
- SSL/TLS Certificates (subject, issuer, validity, SANs)
- Cipher Suites (SSL 2.0 → TLS 1.3)
- Vulnerability Scanning (Heartbleed, ROBOT, CCS Injection, CRIME, etc.)
- HTTP Security Headers (HSTS)
- SSH Fingerprinting (banner, version, host keys, algorithms)
- SMTP Security (encryption, authentication methods)
Application Layer
- HTTP Fingerprinting (headers, cookies, redirects, CDN/WAF detection)
- Port Scanning (common service ports)
- OS Detection (TTL-based fingerprinting)
- SSH Server Analysis (port 22)
- SMTP Server Analysis (ports 25, 587, 465)
Performance
- Parallel Mode (4-5x faster scans)
- Serial Mode (safer, easier to debug)
- Configurable modules (enable/disable any scan)
- Real-time status updates
Example settings
Pro-tips:
- Use the "Only trigger when unique lines appear in all history" text filter setting to limit to new events that has not been seen before (ignores text moving around like IP addresses in a pool).
📦 Installation
This processor agent is only used with changedetection.io
docker-compose.yml based installations.
Uncomment and/or add this package to the EXTRA_PACKAGES var in docker-compose.yml of your changedetection.io installation.
environment:
- EXTRA_PACKAGES=changedetection.io-osint-processor
EXTRA_PACKAGES is a space-separated list of extra packages to add at startup time to changedetection.io.
Standalone pip3 installations.
pip3 install changedetection.io-osint-processor
⚠️ Note: Requires cryptography>=43,<45 for sslyze compatibility.
🔒 SOCKS5 Proxy Support
The OSINT processor supports SOCKS5 proxies for enhanced privacy and anonymity. This is perfect for:
- 🧅 Tor onion routing (
socks5h://127.0.0.1:9050) - 🛡️ Anonymous reconnaissance without exposing your IP
- 🌍 Geolocation bypass via SOCKS5 proxy servers
- 🔐 Privacy-focused monitoring of sensitive targets
⚠️ CRITICAL SECURITY WARNING: DNS Leaks
Always use socks5h:// (not socks5://) to prevent DNS leaks!
- ✅
socks5h://127.0.0.1:9050- Remote DNS resolution (secure) - ❌
socks5://127.0.0.1:9050- Local DNS resolution (LEAKS YOUR QUERIES)
The h in socks5h:// forces hostname resolution through the SOCKS5 proxy, preventing your DNS queries from leaking to your local DNS server.
What we do to prevent leaks:
- DNS scans use TCP (port 53) through SOCKS5 - no local DNS
- HTTP scans skip local DNS resolution when proxy is configured
- SSH/SMTP pass hostnames to proxy - remote DNS only
- If SOCKS5 connection fails, we block the request (no fallback to direct connection)
Without these protections, your real IP and DNS queries would be exposed even when using a proxy!
Supported Steps:
| Step | SOCKS5 Support | Notes |
|---|---|---|
| DNS Records | ✅ Supported | Uses DNS-over-TCP (port 53) through SOCKS5 |
| HTTP Fingerprinting | ✅ Supported | Full proxy support via requests library |
| SSH Fingerprinting | ✅ Supported | TCP connections proxied via python-socks |
| SMTP Fingerprinting | ✅ Supported | MX server scans through SOCKS5 proxy |
| DNSSEC Validation | ⚠️ Partial | DNS-over-TCP possible (not yet implemented) |
| Email Security (SPF/DMARC/DKIM) | ⚠️ Partial | DNS-over-TCP possible (not yet implemented) |
| WHOIS Lookup | ⚠️ Partial | TCP port 43 compatible (library limitation) |
| TLS Analysis | ⚠️ Partial | TCP-based but SSLyze doesn't support SOCKS5 |
| Port Scanning | ❌ Not supported | Raw socket connections |
| Traceroute | ❌ Not supported | ICMP/UDP packets incompatible |
| BGP/ASN Info | ❌ Not supported | API lookups (not yet implemented) |
| OS Detection | ❌ Not supported | Raw socket fingerprinting |
| MAC Address Lookup | ❌ Not supported | Layer 2 local network only |
Note: When a SOCKS5 proxy is configured, unsupported steps are automatically skipped and listed in the scan output.
⚠️ Important: Only SOCKS5 proxies are supported. HTTP/HTTPS proxies will be rejected with an error message.
🚀 Quick Start
- Create a watch with URL:
https://example.com - Select processor: OSINT Reconnaissance
- Configure OSINT Settings (optional):
- DNS Server: 8.8.8.8 (or 1.1.1.1, 9.9.9.9)
- Scan Mode: Serial or Parallel
- Enable/Disable modules as needed
📊 Sample Output
Target: https://example.com
Hostname: example.com
IP Address: 93.184.216.34
Reverse DNS: example.com.
=== BGP / ASN Information ===
ASN: 15133
Organization: Edgecast Inc.
Country: US
=== DNS Records ===
A Records: 93.184.216.34
AAAA Records: 2606:2800:220:1:248:1893:25c8:1946
NS Records: a.iana-servers.net., b.iana-servers.net.
=== SSL/TLS Analysis (SSLyze) ===
Certificate: CN=www.example.org
Issuer: DigiCert TLS RSA SHA256 2020 CA1
Valid: 2024-01-30 → 2025-03-01
Status: ✓ Valid
=== TLS Security Vulnerability Report ===
Status: ✓ All checks passed
✓ Secure: Heartbleed (CVE-2014-0160)
✓ Secure: ROBOT Attack
✓ Secure: OpenSSL CCS Injection
✓ HSTS: 31536000 seconds
🎯 Use Cases
Security Monitoring
- Certificate expiry alerts
- Vulnerability detection (TLS/SSL)
- DNS hijacking detection
- TLS configuration monitoring
Infrastructure Tracking
- IP address changes
- Nameserver updates
- Network path changes (traceroute)
- ASN migrations
Compliance & Audit
- TLS standards compliance
- Security headers monitoring
- Port exposure tracking
- Certificate transparency
⚙️ Configuration
Scan Modes
- Serial (Default): Safer, easier to debug, 30-60s typical
- Parallel: 4-5x faster, higher resource usage, 10-20s typical
Module Selection
- Fast Scan (15-20s): DNS, WHOIS, HTTP, basic TLS
- Comprehensive Scan (60-90s): All modules + vulnerability + port scanning
DNS Servers: 8.8.8.8 (Google), 1.1.1.1 (Cloudflare), 9.9.9.9 (Quad9)
🔧 Advanced Features
- Auto-discovery: Automatically includes new sslyze vulnerability checks
- IP Detection: Auto-detects IPv4/IPv6, skips DNS when needed
- Real-time Status: Live scan progress updates
- Configurable: Per-module enable/disable controls
🐛 Troubleshooting
Cryptography Conflicts: pip install 'cryptography>=43,<45'
TLS Scan Failures: Normal for HTTP-only sites, IPs without TLS, or closed ports
Slow Scans: Use Parallel mode, disable Port Scanning or Vulnerability Scanning
📄 License
GNU Affero General Public License v3.0 (AGPL-3.0)
This ensures any modifications made to this software when running as a network service must be shared with users.
🙏 Credits
Built with: changedetection.io, sslyze, dnspython, python-whois, mac-vendor-lookup
Made with ❤️ for the OSINT community
Metadata
Release files for changedetection.io-osint-processor 0.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| changedetection_io_osint_processor-0.0.4.tar.gz | 58.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| changedetection_io_osint_processor-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 131.1 kB
Release files / changedetection_io_osint_processor-0.0.4.tar.gz
| Download URL | changedetection_io_osint_processor-0.0.4.tar.gz |
|---|---|
| Size | 58.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee4eb0df2448b5d5d89df022acef0168b96ba31bb3e450ac4f91c0f476224406
|
|
BLAKE2b-256 checksum How to use checksums |
fc91a5a7258bda053ebffc923aa81f21000f9b94768c74bd7ed3da6e83831026
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 5, 2026.
Transparency logRelease files / changedetection_io_osint_processor-0.0.4-py3-none-any.whl
| Download URL | changedetection_io_osint_processor-0.0.4-py3-none-any.whl |
|---|---|
| Size | 72.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2964121d22e44866aa4e07a060ec5bf1d694b3f4ba530db3c00c6d4c43448222
|
|
BLAKE2b-256 checksum How to use checksums |
a5792bc82c54a5b87cf89671504786e4597b5a3d1570676d1110fa5f155a679e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 5, 2026.
Transparency log