Public Trust Index

What the internet’s trust infrastructure actually looks like

Measured counts from the sources LayerCall scores against — registry records, operator-published server lists, and the Tor Project’s own exit list. Updated weekly. Free to quote or cite, with attribution.

As of 27 July 2026 (UTC).

8,179
Disposable-email domains tracked
9,518
Published VPN exit nodes
1,387
Live Tor exit nodes
98
RIPE-verified ASNs

Which TLDs host disposable email

Share of 8,179 known disposable-email domains, by top-level domain.

TLDDomainsShare 
.com2,84434.77%
.net7789.51%
.org4135.05%
.de2192.68%
.top1892.31%
.ru1722.1%
.cc1712.09%
.uk1591.94%
.us1561.91%
.info1491.82%
.cfd1221.49%
.store1221.49%
.site1191.45%
.xyz1171.43%
.tk1001.22%

A TLD appearing here does not make its domains untrustworthy — .com leads mostly because .com is enormous. What matters for scoring is the specific domain, never the suffix alone.

VPN exit infrastructure, as published by the operators

Counted from each provider's own public server API — the same lists their apps use to pick a server.

ProviderExit nodesCountries
NordVPN8,943149
Mullvad57550

This ranks published infrastructure, not market share or quality. Operators who publish a server list appear here; those who do not are absent regardless of size. That is a fact about transparency, not about how many people use them.

How this is measured

Every figure above, and where it comes from.

  • Disposable-email domainsdisposable-email-domains (public blocklist)
  • Tor exit nodesThe Tor Project — official bulk exit list
  • NordVPN exit nodesNordVPN public server API
  • Mullvad exit nodesMullvad public relay API
  • Datacenter and VPN ASNsLayerCall ASN table, verified against RIPE

No figure on this page is derived from customer traffic. These are counts of publicly published infrastructure, recomputed weekly from the primary source in every case — not resold from an aggregator.

Citing this page

Quote any figure with a link back to this page. If you need the underlying numbers as JSON, or a cut that is not shown here, ask — we would rather the number be reported correctly than approximately.

Request the data