reportedip.com valid

ReportedIP Documentation

Community-driven IP reputation service: REST API, blacklist feeds, WordPress

For agents: Community-driven IP reputation service with a REST API, blacklist feeds, a free WordPress security plugin, and DNS health checking tools.

ip reputationblacklist feedrest apiwordpress securitydns checkerspf dkim dmarc

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T19:43:59.294Z. Cached copy · Source on reportedip.com

# ReportedIP Documentation

> Community-driven IP reputation service: REST API, blacklist feeds, WordPress
> security plugins, honeypot server and DNSBL zone. Operated from Germany under GDPR.

Docs root: https://reportedip.com/docs/

## Products

- [ReportedIP Hive](https://reportedip.com/products/wordpress-plugin/): Real-time WordPress security with 16 detection sensors, a Web Application Firewall, four 2FA methods and an opt-in community threat network. Free and open source forever.
- [ReportedIP Agent](https://reportedip.com/products/linux-agent/): One static binary that puts thousands of known attackers into your kernel firewall before they reach you, and watches every log your server already writes for the ones nobody has reported yet.

## Data

- [Public API](https://reportedip.com/products/api/): The reputation engine behind everything. Query IPs, submit reports, pull the blacklist and run bulk operations from any language, your SIEM, your firewall or your hosting panel.
- [Blacklist Feed](https://reportedip.com/docs/blocking/blacklist/): Community-driven blacklist, automatically scored from real-time reports. Plain text, JSON and CSV, ready for iptables, nftables, nginx or any blocklist consumer.
- [DNS / RBL Zone](https://reportedip.com/products/dnsbl-zone/): Ask a DNS question instead of downloading a list: your mail server looks the address up live, the same way it already queries Spamhaus. No imports, always fresh.

## Free Tools

- [DNS Checker](https://reportedip.com/dnschecker/): Domain health diagnostics from about 100 resolvers in more than 50 countries. Validate SPF, DKIM, DMARC and DNSSEC, run DNSBL lookups and track propagation during migrations.
- [Reverse DNS Lookup](https://reportedip.com/reverse-dns/): Resolve the PTR record of an IPv4 or IPv6 address and check whether it resolves back. A PTR record nobody confirms is the most common reason a mail server is refused at the door.
- [DNSBL Blacklist Check](https://reportedip.com/dnsbl-checker/): Look up an address or domain across curated blacklists at once and see which one lists it, so you know where to ask for removal.
- [Email Security Check](https://reportedip.com/email-security-check/): Check the seven records that decide whether your mail is trusted and delivered encrypted, and get told which one is missing, too permissive or contradicting another.
- [SPF Generator](https://reportedip.com/spf-generator/): Build the SPF record from the services that send your mail, with the real number of DNS lookups for every include. Loads what you publish today and merges it.
- [DMARC Generator](https://reportedip.com/dmarc-generator/): Write a DMARC record that follows RFC 9989, with a dated plan from p=none to p=reject and the extra record an external report mailbox needs.
- [DKIM Generator](https://reportedip.com/dkim-generator/): Create an RSA or Ed25519 key pair in the browser and get the DNS record in the format your DNS panel accepts. Checks the key once it is published.
- [M
…

Related sites

Other listed sites in Cybersecurity. See the whole category →

Machine-readable: GET /v1/resolve?q=reportedip.com · GET /v1/domain/reportedip.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for reportedip.com:
1. POST https://agentwebmap.com/v1/sites/reportedip.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://reportedip.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/reportedip.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/reportedip.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.