Trust
Network & allowlisting
If your test environment can only reach allowlisted hosts, these are the names to allow for the hosted service. They are stable: endpoints may gain names, but these keep working. api.testlie.com is permanent, so it is the name to put in allowlists and base URLs that should never change. Every one is under testlie.com, so an allowlist of testlie.com and *.testlie.com covers them all.
| Host | Ports | What uses it |
|---|---|---|
api.testlie.com |
443 | Everything your servers call: API mocks (/mock/…), the Twilio-compatible SMS and voice API, the WhatsApp and push sandboxes, mock IdPs, request bin capture URLs (/in/<token>) and the REST API (/api/…) |
testlie.com |
443 | The same endpoints. Base URLs shown in the app use this name |
app.testlie.com |
443 | The dashboard, sign-in and the MCP endpoint |
smtp.testlie.com |
25, 587, 2525 (STARTTLS), 465 (TLS) | SMTP for inboxes |
smtp.testlie.com |
2775, 3550 (TLS) | SMPP for SMS accounts |
Using api.testlie.com
api.testlie.com answers every integration path that testlie.com does, so you can swap the host in any base URL: https://testlie.com/mock/<slug> becomes https://api.testlie.com/mock/<slug>, and a request bin's capture URL becomes https://api.testlie.com/in/<token>. Browser pages, such as sign-in and the dashboard, redirect to app.testlie.com.
Two things don't change with the host:
- Mock IdP issuers stay
https://testlie.com/idp/<slug>, and OIDC libraries compare the issuer with the discovery URL. Point identity libraries attestlie.comand allow that name too. The Microsoft preset's Microsoft's issuer setting is the exception: its tokens namelogin.microsoftonline.com. - Request bins never render HTML here. A bin response with
Content-Type: text/htmlis sent as plain text onapi.testlie.comandtestlie.com. Only the separate user-content domain,testusercontent.com, renders it, sandboxed. Allow that domain only if a browser in your tests opens bin responses or message previews.
Addresses
api.testlie.com, testlie.com and app.testlie.com are served through Amazon CloudFront, whose addresses change. Allow them by name (most egress proxies and firewalls resolve allowed names themselves), or use CloudFront's published ranges (the CLOUDFRONT service in AWS's ip-ranges.json). smtp.testlie.com points straight at the server's fixed address, so resolving it once is enough for an IP allowlist.
Requests from Testlie to your systems (webhooks, mock webhooks, voice and status callbacks) currently leave from that same server. To let them into your network, allow the address smtp.testlie.com resolves to.
Self-hosting? The integration alias is the INTEGRATION_HOSTS setting of the bundled Caddy configuration.