Email Marketing & Newsletter
Inxmail
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Inxmail GmbH · www.inxmail.de
Compare with Klaviyo → Compare with rapidmail → Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Inxmail GmbH of Freiburg, Germany, sells enterprise email marketing in three modules: newsletters and campaigns, transactional emails, and SMTP mail relay. The bench's scoring favours its connection surface — integrations at 6-7, crediting self-service SOAP and REST APIs with public documentation, a Commerce API for transactional workflows, and named connections to Shopify, Magento, Shopware, OXID, Salesforce and Microsoft Dynamics. List data control followed at 5-6, on documented bidirectional export of recipient responses, delivery information and subscription states into your own warehouse or CRM. The weakest area is sovereignty at 2-3: the captured pages name Inxmail GmbH, and we found no public information on data residency, ownership or subprocessors. Deliverability held flat at 4 — authentication is described only in general terms, with no public information on SPF, DKIM or DMARC setup. Judges split on consent and proof at 3-4: those crediting optional tracking and the double opt-in shown in two integrations scored higher; those weighing the undocumented consent record scored lower. Campaign and automation spread 4-6, with no public information on A/B testing, send-time optimisation or holdout measurement.
Speaks for it
- Self-service SOAP and REST APIs with public documentation, plus a Commerce API that triggers events and returns transaction results.
- Bidirectional export automation stores recipient responses, delivery information, subscriptions and unsubscriptions in your own campaign tool or data warehouse.
- Open- and click-rate tracking is offered as an optional service rather than always on.
- Named integrations span Shopify, Magento, Shopware, OXID, Spryker, WEBSALE, Salesforce and Microsoft Dynamics, with partner platforms covering over 100 and more than 300 systems.
- Automatic bounce management, domain-authorisation protection and a named deliverability team, with a stated spam-rate requirement below 0.3 percent.
Held against it
- We found no public information on data residency, ownership or any subprocessor in the chain behind a send.
- Authentication is described only in general terms, with no public information on SPF, DKIM or DMARC setup, dedicated IPs or warm-up.
- We found no public information on what the consent record contains, on unsubscribe handling, or on retention rules.
- We found no public information on documented deletion of a subscriber across all records, on export throttling, or on full-account export.
- The captured pages show no price figures; the entry path is a personal live demo and a free test.
Best for
- You run a DACH commerce stack on Shopify, Magento, Shopware or OXID and want campaign, transactional and SMTP relay sends from one vendor.
- You want recipient responses, delivery information and subscription states flowing into your own CRM or data warehouse.
- Your developers build against documented, self-service APIs and want to trigger transactional sends from your own application.
Avoid if
- Your sign-off requires documented SPF, DKIM or DMARC setup — the captured pages describe authentication only in general terms.
- You expect per-segment personalisation in the base package — dynamic content is sold as a separate add-on.
- You need double opt-in as a documented platform default — it appears on the captured pages only inside the Shopware and Meta Lead Ads integration descriptions.
The scores
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — One-off broadcasts from a fixed template; no segmentation and no automation of any kind.
3 — A drag-and-drop editor and simple list segmentation, but automation is a single welcome mail and there is no testing.
5 — Reusable templates, attribute and behaviour segmentation, multi-step automations on common triggers, and subject-line A/B testing.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, and testing that reports significance rather than raw counts.
10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.
The CRM Manager
A visual drag-and-drop workflow editor with templates for common sequences, an audience editor that segments on attributes and purchasing behaviour, and dynamic personalised content as a documented add-on are the bones of a real lifecycle programme. I found no public information on A/B testing, send-time optimisation or holdout measurement, so I cannot credit anything on the testing and measurement side that a programme owner would build on. 6 8 11
The Deliverability Engineer
A visual drag-and-drop workflow editor with templates for common sequences, segmentation on attributes and purchasing behaviour, and dynamic personalized content as an add-on; event triggers arrive from other systems through the Commerce API. We found no public information on A/B testing, send-time optimisation, or holdout measurement. 6 8 10
The Data Protection Officer
A drag-and-drop editor, reusable templates, a visual workflow builder with templates for common sequences, and segmentation by language, location and purchasing behaviour with dynamic content per group are documented, and transactional sends are triggered from order events. We found no public information on A/B testing, send-time optimisation, holdout measurement or testing that reports significance, so this sits in the middle of the range rather than above it. 6 8 10
The Shop Owner
A drag-and-drop editor, visual workflow builder with templates for common sequences, segmentation by purchasing behaviour, and a dynamic-content add-on are documented, and the Shopify connection mentions automated workflows. We found no public information on A/B testing, journey branching, send-time optimisation or abandoned-cart flows specifically. 6 8 11
The Integrator
The captured pages show a drag-and-drop editor, an audience editor segmenting on language, location and purchasing behaviour, visual workflows with templates for common sequences, and dynamic content as an add-on — most of a solid mid-level package. We found no public information on A/B testing, send-time optimisation or holdout measurement, so the testing dimension stays unevidenced. 6 8
The Skeptic
A drag-and-drop editor, an audience editor segmenting by language, location and purchasing behaviour, and a visual workflow builder with templates for common sequences are documented, plus a dynamic-content add-on for per-segment personalisation. We found no public information on A/B testing, send-time optimisation or holdout measurement, which is what separates this from a higher band. 6 8
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — No documentation of authentication or bounce handling; deliverability appears only as a marketing number.
3 — SPF and DKIM setup documented, but no DMARC guidance, no stated bounce policy and shared sending only.
5 — SPF, DKIM and DMARC documented with a custom sending domain, automatic hard-bounce suppression, and complaint-loop handling stated.
8 — The above plus dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, and published guidance on list hygiene.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
Automatic handling and tracking of delivery errors is documented, and a deliverability team with consulting plus a stated spam-rate guardrail of 0.3 percent is more substance than a marketing inbox figure. But the captured pages name no authentication protocols and I found no public information on SPF, DKIM or DMARC setup, dedicated IP options, warm-up or inbox-placement testing. 8
The Deliverability Engineer
Bounce management is documented as automatic handling and tracking of delivery errors, protective mechanisms hold the spam rate below 0.3 percent, and a deliverability team is named as included — but authentication is asserted in one word rather than documented as SPF, DKIM or DMARC setup, and we found no public information on dedicated IPs, warm-up, or engagement-based sunsetting. The "high delivery rate" line on the sending servers is a number I discount on principle. 8
The Data Protection Officer
Sending on the vendor's own servers, automatic handling and tracking of delivery errors, a stated spam-rate requirement below 0.3 percent, and a deliverability team that diagnoses and eliminates spam-folder causes are all documented. We found no public information on SPF, DKIM or DMARC setup guidance, dedicated IP options with warm-up, complaint-loop handling or inbox-placement testing, so the authentication layer rests on a generic promise of authentication rather than documented protocols. 8
The Shop Owner
Automatic bounce handling, a deliverability team that consults when mail lands in spam, domain-authorization protection, and a stated requirement that the spam rate stay below 0.3 percent are on record. We found no public information on SPF, DKIM or DMARC setup guidance, dedicated IP options, warm-up or inbox-placement testing. 8
The Integrator
Authentication, automatic bounce management and delivery-status feedback into customer systems are documented, and a spam-rate limit of 0.3 percent plus a named deliverability team read as an enforced policy rather than a marketing number. We found no public information on SPF, DKIM or DMARC setup, custom or dedicated sending domains, warm-up or inbox-placement testing. 8
The Skeptic
Automatic bounce handling, a requirement that the spam rate stay below 0.3 percent, domain-authorisation protection and a deliverability team that diagnoses spam-folder causes are documented. But we found no public information naming SPF, DKIM or DMARC setup, custom sending domains, dedicated IPs or warm-up — authentication appears only as a generic word in the relay copy. 8
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Single opt-in with no consent record; tracking is always on and cannot be disabled.
3 — Double opt-in available but not the default, and the consent record is a timestamp without the source, IP or the wording consented to.
5 — Double opt-in as the documented default with a stored consent record including source and timestamp, one-click unsubscribe, and tracking that can be turned off per campaign.
8 — Consent is reproducible as evidence: the confirmation mail and form wording versioned and retrievable per subscriber, unsubscribe honoured across lists, tracking off-by-default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Tracking and reporting are an optional integration rather than always-on, which I rate, and double opt-in appears in the Shopware and Meta Lead Ads integrations with consents named as data you can transfer to a leading system. Beyond that I found no public information on a platform-wide consent record, its source and wording, unsubscribe handling across lists, or retention rules for inactive subscribers. 8 10 11
The Deliverability Engineer
Tracking and reporting are optional rather than built in — open and click tracking is listed as an optional service — and consents are handled as data that syncs to your leading system. Double opt-in appears only inside two integration descriptions rather than as a documented default, and we found no public information on what the consent record stores, unsubscribe handling, or retention rules for inactive subscribers. 8 10 11
The Data Protection Officer
Tracking and reporting are documented as optional throughout, and on the SMTP relay product open and click rate tracking is even listed as an optional service rather than included — that is exactly the switch I look for before signing off. Double opt-in appears only inside integration descriptions for Shopware and Meta Lead Ads, and we found no public information on the consent record itself, its source and wording, unsubscribe mechanics, retention rules or the handling of access and erasure requests, so the proof that survives a complaint is not evidenced. 8 10 11
The Shop Owner
Double opt-in appears in the Shopware and Meta lead connections, consents are transferable to a leading system, and open- and click-rate tracking is an optional service rather than always on. We found no public information on what the consent record contains, one-click unsubscribe, unsubscribe handling across lists, or a preference centre. 8 10 11
The Integrator
Double opt-in appears in specific connectors (Meta Lead Ads, Shopware) and consent is listed as data transferable to a leading system, but we found no public information on what the consent record contains, one-click unsubscribe, or access and erasure handling. Tracking and reporting being optional is a genuine point in the vendor's favour here. 8 10 11
The Skeptic
Tracking can genuinely be left out — open and click tracking is listed as an optional service and the platform's tracking is described as optionally integrable — and double opt-in appears in the Shopware and Meta Lead Ads integration descriptions. We found no public information on the consent record itself, unsubscribe handling, a preference centre, or whether double opt-in is the default anywhere on the platform. 8 10 11
List ownership, import & exit
Show reasoningHide reasoning
How this is scored
Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
0 — Export is addresses only; engagement history, segments and automations cannot leave.
3 — CSV import and export of subscriber fields, but engagement history and unsubscribe state are not exportable.
5 — Full subscriber export including custom attributes, subscription status and unsubscribe state, plus API access sufficient to sync elsewhere.
8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.
10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.
The CRM Manager
Bi-directional synchronisation is genuinely evidenced: recipient responses, delivery information, tracking data, subscriptions and unsubscriptions flow into your campaign management tool or data warehouse, alongside automated CSV import and a self-service API. I found no public information on documented deletion of a subscriber across all records, export throttling, or exporting campaigns and templates, which is the line between a good sync and a true exit. 10
The Deliverability Engineer
Export automation is bidirectional and pushes recipient responses, delivery information, subscriptions, unsubscriptions and consents into your own campaign management tool or warehouse in real time, so engagement history clearly leaves the platform. We found no public information on documented deletion of a subscriber across all records, on export formats and throttling, or on full-fidelity export of the whole account. 10
The Data Protection Officer
Automated CSV import, bidirectional synchronisation that stores recipient responses and delivery information in the customer's campaign management tool or data warehouse, subscription and unsubscription state flowing to CRM systems, and real-time API transfer of recipient data and statistics are documented. We found no public information on documented deletion of a subscriber across all records, on export of campaigns and templates, or on any export throttling, which is why I stop short of the higher marks. 10
The Shop Owner
Recipient data, responses, delivery information and subscription states flow both ways via the documented REST/SOAP API, automated CSV exchange and bi-directional export automation, so engagement history lands in my own warehouse. We found no public information on documented deletion of a subscriber across all records, full-account export or export throttling. 10
The Integrator
Bi-directional export automation is documented to carry recipient responses and delivery information into a campaign management tool or data warehouse, and the use cases name synchronising subscriptions and unsubscriptions with the CRM — enough to move the list and its history elsewhere. We found no public information on documented deletion of a subscriber across all records, export throttling, or full-account export. 10
The Skeptic
Automated CSV import and a bi-directional export automation that pushes recipient responses and delivery information into a warehouse or campaign tool are documented, with a REST API carrying recipient data, content and statistics in real time. We found no public information on documented deletion across records, export of campaigns and templates, or exit terms. 10
Integrations & API
Show reasoningHide reasoning
How this is scored
The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.
0 — No API and no named integrations; the list is maintained by CSV upload.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks for the core subscriber events.
8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.
10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.
The CRM Manager
The strongest surface in the captures: a documented REST and SOAP API usable without a partner agreement, an API to create and send mailings from your own application, a Commerce API that triggers events and returns transaction results, and named integrations across Shopify, Magento, OXID, Salesforce, Dynamics and the Zapier, Make and n8n layer. I found no public information on documented rate limits, a sandbox, or webhook retries, which is what holds it short of the top band. 10 11
The Deliverability Engineer
Self-service SOAP and REST APIs with available documentation, transactional sending and event triggers through the Commerce API, and dozens of maintained integrations including Shopify, Magento, Shopware, Salesforce and Microsoft Dynamics, plus wider reach through com:con BAF and Marini. We found no public information on webhooks with retry behaviour, documented rate limits, or a sandbox. 10 11
The Data Protection Officer
SOAP and REST APIs usable independently without a partner agreement, a Commerce API that triggers events and returns transaction results, mailings created and sent directly from external applications, and a broad maintained catalogue spanning Shopify, Magento, Shopware, Salesforce, Microsoft Dynamics, Make, Zapier and n8n are documented. We found no public information on webhooks with retries, documented rate limits, a sandbox environment, or API versioning with a deprecation policy. 8 10 11
The Shop Owner
Shopify, Magento, Shopware, OXID, Spryker, WEBSALE and Nosto are named alongside Salesforce and Microsoft Dynamics, plus a self-service SOAP/REST API, a Commerce API for transaction workflows, and partner frameworks covering hundreds of systems. We found no public information on webhooks, documented rate limits or a sandbox, which keeps this below the top band. 10 11
The Integrator
A self-service SOAP and REST API with documentation, plus a Commerce API to trigger events and read transaction results, is exactly the surface I need, and the catalogue names Shopify, Magento, OXID, Salesforce and Microsoft Dynamics with case studies behind it. But we found no public information on rate limits, webhook retries, a sandbox or a deprecation policy, and a large share of the claimed breadth — Zapier, Make, Marini, Syncler, com:con — routes through third parties rather than vendor-maintained connectors. 10 11
The Skeptic
SOAP and REST APIs with public documentation and self-service connection, a Commerce API that triggers events and returns transaction results, and named bidirectional integrations including Shopify, Magento, OXID, Salesforce and Microsoft Dynamics — with partner platforms claiming over 100 and over 300 systems respectively — make this surface broad. We found no public information on webhooks with retries, documented rate limits or a sandbox, which keeps it short of the top band. 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily.
0 — US vendor and contracting entity, US hosting, subprocessors unnamed; subscriber behaviour leaves the EU with no stated basis.
3 — EU hosting offered as an option or for storage only, while sending, tracking or support access remains non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — sending infrastructure, analytics, support tooling — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, complete subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
The contracting entity is evidenced as Inxmail GmbH with a German CEO and a German-language home market, and that is where confirmation ends. I found no public information on data residency, ownership or a subprocessor list on the captured pages, so the chain a DACH buyer must audit before sign-off is unverifiable from what is published. 8
The Deliverability Engineer
The captured pages name Inxmail GmbH, but we found no public information on where subscriber data and behavioural tracking are hosted, on the contracting entity's jurisdiction, or on a single subprocessor that touches the send. For a buyer who weighs this heavily, undocumented equals unevaluable — even the captured security and privacy pages yielded nothing on residency. 5 8
The Data Protection Officer
A German contracting entity is evidenced on the captured pages, but we found no public information on where subscriber data and tracking data are hosted, on ownership, or on any subprocessor in the chain behind the send. Until the hosting location and the full subprocessor list are published, I cannot answer where the behavioural data lives without an argument I would rather not have to make, and I weigh that heavily here. 8
The Shop Owner
Only the German company identity is on record; we found no public information on where subscriber data is hosted, the contracting entity's jurisdiction, data residency or any subprocessor list. For a buyer who weighs this heavily, that silence decides the score. 8
The Integrator
Inxmail GmbH is named on the vendor's own pages and the vendor is presented as based in Germany, which rules out the offshore scenario, but we found no public information on where subscriber data and behavioural tracking are hosted, on the contracting entity's jurisdiction beyond the company name, or on subprocessors and certifications. I weight this heavily, and an unconfirmed chain with no published subprocessor information caps it low. 8
The Skeptic
The captured pages name the vendor as Inxmail GmbH with a named CEO, but we found no public information on where subscriber data is hosted, the contracting entity's jurisdiction, ownership, or any subprocessor list. Even the security and data-protection page as captured contributes nothing on hosting or subprocessors, so nothing evidences that sending and tracking stay in the EU. 5 8
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A headline price per contact tier exists, but send limits, overage rates or the tier where automation begins are not stated.
5 — Contact-tier prices public with the billing period stated and send limits given, but at least one commonly needed capability sits in an unpriced tier or add-on.
8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.
10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.
The CRM Manager
No price figures appear in the captures at all; what exists is a scope description for the SMTP relay — hosting and administration, one hour of user support per month and deliverability team assistance included, open and click rate tracking as an optional service — with a demo request as the entry point. A buyer cannot compute any invoice for their list size or send volume from these pages. 6 8
The Deliverability Engineer
No price figure appears anywhere: the captured pages offer a free test and a live demo, and enumerate what the relay includes — hosting and administration costs, one hour of user support per month, deliverability team assistance — with open and click tracking as an optional service. We found no public information on contact tier prices, send limits, or overage rates. 6 7 8
The Data Protection Officer
No price for any tier, module or add-on appears on the captured pages, and the route to a number is a demo request and a free trial. The SMTP relay page does state what is included and what remains an optional service, but we found no public information on contact-tier prices, send limits, overage rates, feature boundaries by tier or VAT treatment. 6 8
The Shop Owner
No price figures appear on the captured pages: the SMTP relay page lists included and optional services without numbers, and the site steers to a demo request and a free trial. A shop owner cannot compute an invoice for any list size from public information. 6 7 8
The Integrator
The captured pages offer a free test and a personal live demo as the entry path, and the SMTP relay page lists inclusions — hosting and administration costs, 1 hour of user support per month, deliverability team assistance — with no price figures attached. We found no public information on tier prices, contact or send limits, or overage rates. 6 7 8
The Skeptic
No captured page shows a price of any kind — no contact tiers, no send limits, no overage rates, no VAT treatment; the commercial path is a demo request and a free test. The relay page lists included services but attaches no figures to them, so a sender cannot compute any invoice from the public pages. 6 8
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 16 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We could not confirm any compliance information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 54 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 17 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 10 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.inxmail.de Checked 16 Sep 2026 Details →
- 2 Products www.inxmail.de Checked 16 Sep 2026 Details →
- 3 Imprint www.inxmail.de Checked 16 Sep 2026 Details →
- 4 Privacy policy www.inxmail.de Checked 16 Sep 2026 Details →
- 5 Security / trust page — found from the homepage www.inxmail.de Checked 30 Sep 2026 Details →
- 6 Campaigns & automation — found from sitemap www.inxmail.de Checked 30 Sep 2026 Details →
- 7 Campaigns & automation — found from sitemap www.inxmail.de Checked 30 Sep 2026 Details →
- 8 Deliverability infrastructure — found from sitemap www.inxmail.de Checked 30 Sep 2026 Details →
- 9 Deliverability infrastructure — found from sitemap www.inxmail.de Checked 30 Sep 2026 Details →
- 10 Integrations & API — found from sitemap www.inxmail.de Checked 30 Sep 2026 Details →
- 11 Integrations & API — found from sitemap www.inxmail.de Checked 30 Sep 2026 Details →