Quick answer
What does the Sealname transparency report show?
The Sealname transparency report counts, every quarter, suspensions for phishing, malware, botnets, CSAM and fraud that takes money from victims, complaints refused without a decision from a Panamanian court, and every request for customer data by origin, with its outcome. Sealname, a private domain name registration service paid in crypto, with no ID and no KYC, publishes its first report in January 2027, covering launch to 31 December 2026. No figures exist yet.
The report at a glance
| Frequency | Every quarter |
|---|---|
| First report | January 2027 |
| First period covered | From launch to 31 December 2026 |
| Status | Period in progress: no figures published yet |
| Abuse data | Reports of phishing, malware, botnets, CSAM and fraud that takes money from victims: share confirmed, median time to action, suspensions |
| Complaints without a decision from a Panamanian court | Copyright, defamation, political and competitor complaints received, and taken down without a decision from a Panamanian court (our policy: zero) |
| Requests for customer data | By origin: Panamanian court orders, foreign governments and police, lawyers and private companies, UDRP/URS; each granted or refused |
| External measures | Our abuse concentration in ICANN Domain Metrica; our domains listed on the Spamhaus DBL; customer data: none, counts only |
| Format | This page and its Markdown version |
Which figures will the report publish each quarter?
Each quarterly report will publish the same set of metrics, so that one quarter can be compared with the next. The table lists every metric and how it is broken down.
Every metric in the quarterly report
| Metric | What it counts | Broken down by |
|---|---|---|
| Abuse reports received | Every report about a domain registered with Sealname, sent to [email protected] | Category: phishing (incl. pharming), malware, botnets, CSAM, fraud that takes money from victims, spam spreading them |
| Share of reports confirmed | Reports where the evidence showed abuse and led to action, as a share of reports received | Category |
| Median time to action | Time from a well-documented report to the action on the domain, for confirmed reports | Category, next to our target times |
| Suspensions | Domains suspended during the quarter | Reason: phishing, malware, botnets, CSAM, fraud, decision from a Panamanian court, associated-domain check |
| Panamanian court orders | Orders from a Panamanian court for customer data, suspension or transfer | Complied with / contested / open |
| Foreign government and police requests | Requests sent directly by foreign authorities, and those that came back through Panamanian legal process | Refused (direct) / through Panama: granted or not |
| Urgent requests under ICANN rules | Requests about an imminent threat to life, serious bodily injury, critical infrastructure or child exploitation | Answered / refused as not urgent |
| UDRP and URS cases | Trademark disputes in which a provider asked us to confirm the registrant and lock the domain (an ICANN obligation) | Locked and confirmed / decision applied / case withdrawn |
| Requests from lawyers and private companies | Demands for customer data or for a takedown: copyright, defamation, political and competitor complaints | Received / refused without a decision from a Panamanian court |
| ICANN compliance requests | Requests from ICANN Contractual Compliance about our domains | Topic |
| ICANN Domain Metrica abuse concentration | Our share of domains on reputation lists, as measured by ICANN | Phishing, malware, botnet command and control |
| Spamhaus DBL listings | Our domains listed on the Spamhaus Domain Block List | Count during the quarter |
Customer data goes out only on a Panamanian court order (or on an urgent request under ICANN rules) or under an ICANN duty: the rules are in the disclosure policy. Takedowns happen only for phishing, malware, botnets, CSAM and fraud that takes money from victims, or on a decision from a Panamanian court: see the abuse policy.
Why does Sealname publish a transparency report?
Because our policy makes two promises, and both need proof. No takedown on complaint alone, and your data only goes out on a Panamanian court order — the report counts every complaint and every request we refused. The strict exceptions — phishing, malware, botnets, child sexual abuse material and fraud that takes money from victims — need proof too: the report shows how fast we suspend them.
The context explains why. A DNSRF analysis found privacy or proxy services on 65% of 414,218 abuse-listed domains. An ICANN-funded study, reported by PCWorld, showed that banks also use such services. Both facts are true, so the only useful answer is data.
The cost of weak abuse handling is real. Trustname, a registrar that promised its customers protection from takedowns, saw its median phishing rate rise from about 0.7% to about 10% between January and August 2026, per ICANN Domain Metrica. ICANN sent it a termination notice on 27 August 2026.
How will Sealname's figures compare with ICANN's RDRS pilot?
We publish request types that can be read next to ICANN's own figures. ICANN ran a Registration Data Request Service (RDRS) pilot from November 2023 to November 2025. It received more than 3,700 disclosure requests. Of these, 32% concerned intellectual property and 16% came from law enforcement. About one in four requests was approved.
On 12 March 2026, the ICANN Board declined the 18 recommendations for a permanent system (SSAD). Decisions on disclosure therefore stay with each registrar. Ours is simple: a Panamanian court order, or an ICANN duty such as the UDRP, and nothing else. Our report shows the result.
ICANN's RDRS pilot in four figures (ICANN data, not Sealname data)
3,700+
disclosure requests
November 2023 to November 2025
32%
about intellectual property
16%
from law enforcement
About 1 in 4
requests approved
Can anyone check Sealname's abuse level today?
Yes, without waiting for our report. ICANN Domain Metrica has been open to everyone since 18 February 2025. It shows the abuse concentration of each registrar, based on reputation lists, for phishing, malware and botnet command and control. Spamhaus also publishes its Domain Block List (DBL) and its own registrar statistics.
Our report will quote both sources each quarter, next to our own counts. Our target times are published on the abuse page: phishing, malware, botnets and fraud that takes money from victims are acted on within 24 hours of a well-documented report.
How are the figures produced?
The figures come from the records of our abuse desk and from our log of legal requests.
- Each request is counted once, in the quarter it was received.
- A request that covers several domains counts as one request.
- The outcome is the one at the end of the quarter. Open cases are shown as open.
- Median times are computed on confirmed reports only.
- Customers and requesters are never named.
The report never contains customer data. Sealname holds little of it anyway: no ID, no postal address and no phone number. The list is on the page data we collect. Prices for private domains are on the price list.
Transparency report: FAQ
Why does the Sealname transparency report have no figures yet?
Because the first reporting period (launch to 31 December 2026) is still in progress. We publish no number before a period closes, and we never estimate one. The first report will be published on this page in January 2027, then a new report every quarter.
When is the first transparency report published?
In January 2027. It covers the first period (launch to 31 December 2026). After that, a report is published every quarter, with the same metrics, so that quarters can be compared. Until then, this page lists the metrics, with no figures.
Will refused requests be published too?
Yes. Every request is counted, whatever its outcome. That applies to Panamanian court orders, foreign government and police requests, requests from lawyers and private companies, and UDRP and URS cases. ICANN compliance requests are counted as well. Refusals show how many requests were not a Panamanian court order or an ICANN duty.
Will the report name customers or domains?
No. The report publishes counts, shares and median times only. It never names a customer, a customer's domain, an email address or a requester. Each figure is a total for the quarter. Sealname holds no ID, no postal address and no phone number in any case.
How can I check Sealname's abuse level myself?
Use ICANN Domain Metrica, open to everyone since 18 February 2025. It shows each registrar's abuse concentration from reputation lists. The Spamhaus Domain Block List shows listed domains. Our quarterly report will quote both, next to our own counts. Neither source depends on Sealname.
Why compare with ICANN's RDRS pilot?
Because it is a large, public set of disclosure figures, published by ICANN itself. The pilot received more than 3,700 requests between November 2023 and November 2025. Of these, 32% concerned intellectual property and 16% came from law enforcement. About one in four was approved. Using the same request types makes our figures comparable.
What counts as a disclosure request?
Any request for customer data that is not public: Panamanian court orders, foreign government and police requests, requests from lawyers and private companies, and UDRP and URS cases. ICANN compliance requests are counted on a separate line. Customer data goes out only on a Panamanian court order (or on an urgent request under ICANN rules) or under an ICANN duty: see the disclosure policy.
Sources (6)
- ICANN's RDRS two-year pilot: what we learned and where we go next — ICANN (3 March 2026)
- ICANN Domain Metrica release update: access now open to all users — ICANN (18 February 2025)
- Notice of termination of the Registrar Accreditation Agreement (Trustname) — ICANN (27 August 2026)
- Privacy/proxy services: a safe haven for cybercriminals? — DNS Research Federation (checked 8 October 2026)
- Exposing hidden domain registrations could hurt innocent users more than criminals — PCWorld (checked 8 October 2026)
- More domain stats: the 10 most abused registrars — Spamhaus (checked 8 October 2026)
Rules first, figures next
Read how requests are decided and how abuse is handled. The first figures arrive in January 2027.