Email glossary · Practical guide
IP reputation: identify the actual sending infrastructure
IP reputation concerns a network address involved in mail delivery. The relevant address may belong to the mailbox provider rather than the server hosting your outreach application.
Reviewed · Examples are illustrative
Who this helps: Readers checking a term before making an outreach or mailbox decision.
Meaning and common confusion
When an app submits through a hosted mail service, the recipient typically sees that service's outgoing infrastructure. Diagnose the actual route before requesting a dedicated IP or filing a listing appeal. A server's web-hosting address is not automatically the source of outbound mail.
Worked example
This is a synthetic illustration, not a customer result or a live configuration to copy.
App host: sends an authenticated submission to Provider A
Recipient connection: comes from Provider A's outbound IP
Investigation target: the observed mail-path IP
Do not assume changing the app's web-host IP changes the provider's delivery reputation.Checks to make
- Read the relevant received-path evidence.
- Identify who controls the address.
- Distinguish shared infrastructure from a dedicated sending arrangement.
Next step and limits
Use shared-versus-dedicated IP guidance for a real infrastructure decision. Dedicated does not mean trusted, and control of an IP does not remove recipient-policy obligations. Zintara does not allocate a dedicated provider delivery IP merely by connecting a mailbox.
Source: Zintara product context for this operational definition
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- Shared vs dedicated sending IP: establish who controls the decision →
- Domain vs IP blocklists: identify the listed object and affected path →