IP widgets and privacy-safe embedding

Embedding an IP widget adds a page dependency: iframe or JavaScript, network requests, caching and logging. An embedded speed test or IP widget should be evaluated for HTTPS/CSP compatibility, performance budget, availability and the technical data visible to the third party.

What to test before publishing

Test responsive layout, loading behaviour, blocked third-party requests and the privacy notice. Do not pass secrets or personal data in query strings. For an IP widget, remember that a public IP is network metadata and can appear in server logs.

The detail that matters

An IP widget should display only the information required for its purpose and should not place IP-derived or account data into public cache keys or URLs. Document third-party requests and retention where applicable, and make failure of the widget non-blocking for the host page. To see the corresponding 2ip widget in practice, open 2ip IP widget.