elitesystem.net

Privacy policy

Last updated: August 17, 2026

Information processed by the service

EliteSystem processes the minimum information needed to operate public tools, decentralized identity lookups, authentication, security rate limits, and administrative audit records. Public tool inputs are not stored as application data.

Bitcoin tools

The fee planner, descriptor generator, PSBT inspector, transaction planner, unsigned PSBT builder, xpub explorer, QR generator, BIP39 wallet generator, and BIP39 recovery checker run entirely in the browser. The address inspector and raw transaction decoder send the submitted value to the EliteSystem server for deterministic decoding, but the application does not store the request body. Never submit seed phrases, private keys, WIF values, wallet passwords, or other secret wallet material to server-processed tools.

Network lookups (WHOIS/RDAP)

The WHOIS tool cannot answer from this server alone: a domain, IP address, or AS number you submit is transmitted to the authoritative registry for that object, which may be IANA, a regional internet registry such as ARIN, RIPE NCC, APNIC, LACNIC, or AFRINIC, or a domain registry or registrar. Those operators are independent controllers and apply their own logging and privacy terms. For a domain whose registry holds no registrant data, the lookup follows the registry's own referral to the registrar, so a second operator receives the same domain name. If you request the optional BGP origin enrichment, the IP address is also sent to the Team Cymru mapping service. Only the value you submit is forwarded; your IP address, account, and session are not.

The result shows the complete record published by the registry or registrar, including names, postal addresses, e-mail addresses, phone numbers, and raw port-43 WHOIS text when those fields are present. Many authorities redact some or all contact fields before publishing a response; EliteSystem preserves that authority-side redaction but does not add a second redaction layer.

Your own IP address

The address lookup tool and the plain-text /ip endpoint report the address your request arrived from, and look that address up against the same registries described above in order to name the network operator, the autonomous system, and the country of allocation. Approximate city and region first come from an operator-published RFC 8805 geofeed. When no matching geofeed is available, the server reads a local DB-IP City Lite database; it does not send your address to DB-IP. The response is marked as non-cacheable and carries no cross-origin permission, so another website cannot read it.

Complete registry responses are held only in memory for a short cache period and are never written to disk. Registry records are published for technical and operational purposes: bulk collection, redistribution, and any use for advertising or unsolicited contact are not permitted, and usage limits apply.

DNS, email, and TLS inspection

A domain, public IP address, or URL submitted to the DNS tool is resolved by a dedicated validating resolver operated by EliteSystem. The email-domain tool uses that resolver to inspect public MX, SPF, DKIM, DMARC, MTA-STS, and TLS-RPT records. DKIM selectors are queried only when you provide them. If the domain advertises MTA-STS, the server fetches its fixed HTTPS policy URL. It does not connect to SMTP or contact DMARC and TLS-RPT report destinations. The TLS tool resolves the same public target and connects only to TCP port 443 to inspect the certificate and protocol. Private, loopback, link-local, documentation, and reserved destinations are rejected. Inputs and results are not stored as application data.

Advertising and third-party scripts

EliteSystem does not display advertising. The service embeds no advertising, analytics, or tracking script from any third party, and it builds no advertising identifier, behavioural profile, or cross-site tracking cookie. Every script and style loaded by these pages is served from this origin under a strict same-origin content security policy.

Cookies

This service sets only strictly necessary first-party cookies: the session cookie issued after you sign in, short-lived state, nonce, and provider cookies that protect the sign-in exchange, and a short-lived cookie remembering the page you were heading to before signing in. No cookie is used for advertising, profiling, or cross-site tracking. You can control or delete cookies using your browser settings.

Security and retention

Security logs and abuse bans may retain IP address, user agent, route, timestamp, and action outcome for operational protection. Account and identity records remain until removed by an administrator or the account holder where the service provides that option.

Contact

Privacy questions can be submitted through the public contact channels associated with the EliteSystem service.