PeaceWeb Group - Trust & Safety Team

PeaceWeb Group - Trust & Safety Team is tracked from public network records as an institution profile for BTW analyst review. The profile keeps infrastructure resources as evidence and does not promote them into BTW entities. published contact points are separated from person candidates so role mailboxes and teams cannot become people. The export is based on public sources only unless future evidence explicitly raises its validation status. Updates should follow newly published evidence.

PeaceWeb Group - Trust & Safety Team

PeaceWeb Group - Trust & Safety Team is an abuse-role contact entity registered in the public RDAP record for autonomous system AS210907 (STEADCLOUD). Its operational footprint is limited to registry data, with no active routing evidence yet observed, making it a latent governance chokepoint whose significance depends on future network activity or registry changes.

Why It Matters

The impact of this team is contingent. If AS210907 begins announcing prefixes, the abuse contact becomes operational for live traffic, and its responsiveness will affect how quickly abuse incidents are resolved. Registry alterations could also transfer this responsibility to another entity, generating ripple effects for network operators and abuse reporters.

What Public Sources Show

The PeaceWeb Group - Trust & Safety Team is a contact entity embedded in the internet's registry system, listed as the abuse handler for the autonomous system AS210907. It matters because the team occupies a potential governance chokepoint: anyone who wants to report network abuse originating from AS210907 will be directed to this team, and the team's responsiveness—or lack thereof—can affect how quickly malicious activity is addressed.

Public evidence for the team's existence and role is both narrow and official. The RDAP record for AS210907 lists "PeaceWeb Group - Trust & Safety Team" as an abuse-role contact, with an associated abuse mailbox. The autonomous system is registered under the name STEADCLOUD. A second registry source, RIPEstat, confirms that AS210907 is a publicly tracked number resource.

The domain peaceweb.com is reachable and matches the abuse contact domain, but the website currently contains no identifiable trust-and-safety content.

The team's operating surface is limited to the information in the registry layer. It has no known public-facing website, policy page, or documented abuse-handling procedures. No active IP prefix announcements are currently observed for AS210907 in the provided evidence, which means the team's operational significance remains latent: it is contactable, but there is no visible network infrastructure actively sending traffic under that ASN.

The team is organizationally linked to PeaceWeb Group B.V., which appears as a related organization in the same RDAP record.

The core impact mechanism is procedural rather than technical. The abuse contact role funnels complaints to the team; if the team acts on them, it could help stop abuse originating from the AS210907 environment. Conversely, an unattended mailbox would become a silent gap in the internet's abuse-handling ecosystem.

The ASN registration also underpins the routing identity for any future network announcements, meaning that if prefixes become active, the team's abuse-contact role becomes operationally relevant.

Concrete watchpoints center on registry changes and routing evidence. Any modification to the RDAP or WHOIS record for AS210907—such as a new abuse contact, a change of organization, or a mail-address update—would directly alter the team's public profile. The appearance of active BGP announcements or newly assigned IP prefixes under AS210907 would signal that the team is now operationally attached to live infrastructure, raising its relevance.

Conversely, if the registry record becomes stale or the domain peaceweb.com stops resolving, the team's visibility would erode.

The principal uncertainty is the gap between the registry entry and a verifiable operational reality. There is no public source that independently describes this team as a standalone business unit with staff, a mandate, or a track record. No personnel names are linked to it. The absence of routing evidence means the team may be dormant, or it may operate entirely in private, accepting reports without publicly routing traffic.

Until those gaps are filled, the team should be tracked as a registry-significant but operationally unconfirmed contact point.

The primary evidence for this profile comes from the RDAP query at https://rdap.org/autnum/210907, which shows the abuse contact, and from the RIPEstat page at https://stat.ripe.net/AS210907, which confirms the ASN's existence. The domain peaceweb.com (https://peaceweb.com/) is consistent with the abuse contact domain.

Operating Surface

The team serves as the abuse contact for AS210907, meaning that reports of network abuse involving that autonomous system are directed to this entity. Its public role is entirely defined by the RDAP entry; no independent operational or policy documentation has been identified outside the registry.

PeaceWeb Group - Trust & Safety Team merits tracking because the abuse contact function is a critical governance mechanism in internet infrastructure. Changes to this contact or the routing status of AS210907 could signal shifts in accountability for abuse, the activation of new network resources, or the dissolution of a dormant registry entity.

Watchpoints

PeaceWeb Group - Trust & Safety Team is a registry-contact artifact whose infrastructure relevance is currently theoretical. The absence of active routing means the team has no visible operational surface. However, as an abuse contact for a registered ASN, it represents a potential point of accountability that could become consequential if the ASN is activated. Strategically, it is a low-priority watch item until routing evidence appears.

1. Any modification to the AS210907 RDAP record—especially a change in abuse contact or organization—would signal a shift in accountability. 2) The first observed BGP announcement or prefix registration under AS210907 would move the team from registry contact to operational significance. 3) A public abuse-handling policy or personnel listing on peaceweb.com would substantiate its operational existence.

There is no independent description of the team as a business unit; no leadership or staff names are available; no routing evidence exists beyond the ASN record; no corporate registry entry for the trust and safety team itself has been located. These gaps prevent a confident assessment of operational capability.

Sources

• Registry RDAP / WHOIS record - public-source identity and registry context for PeaceWeb Group - Trust & Safety Team.
• RIPE registry record - RIPEstat provides a public overview page for AS210907, supporting that the ASN exists as a publicly tracked internet number resource.
• peaceweb.com - The domain peaceweb.com is publicly reachable and is consistent with the abuse contact domain shown in the RDAP record.