Deployteq uses Deployteq as their primary email service provider. We've also observed sends via HubSpot. Email goes out from 2 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
Authentication signals observed in this brand's emails. SPF, DKIM and DMARC are the standard sender-authentication stack — see the DMARC policy below for whether spoofing is actually blocked or just monitored. One-click unsubscribe meets Google & Yahoo's bulk-sender requirements.
SPF / DKIM / DMARC above reflect the last 2 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to deployteq.com. Policy
p=none is monitor-only — receivers won't act on spoofing yet.
SPF alignment: 33% of observed emails use an aligned return-path (e.deployteq.com); the rest use third-party paths (happyhorizon.com, bf06x.hubspotemail.net) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 24 observed emails sign with a domain aligned with deployteq.com (deployteq.com, e.deployteq.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: modern — 92% TLS 1.3 (across 12 sends).
Delivery: fast — 100% of emails in the last 7 days arrive in under 10 seconds (across 2 sends).
Brands often use multiple ESPs (e.g. one for marketing, another for transactional/notifications).
HubSpot 1ESPs we've seen sending email for this brand. Green = confirmed by SPF, sender IP rDNS, or known infra pairing (label shows the source). Grey = observed but not yet confirmed by SPF or PTR.
ESPs this brand has authorized in their SPF record. We confirm them with a green ✓ only after seeing recurring use (3+ emails across 2+ days). Until then they stay here — either we haven't observed any email yet, or we've seen a handful but not enough to call them a regular sender for the brand.
Probed: deployteq.com, happyhorizon.com, e.deployteq.com, bf06x.hubspotemail.net
Folder distribution across all emails from this brand observed in Gmail inboxes. High inbox % = good deliverability; spam appearances are the headline signal.
| Folder | Count | Share |
|---|---|---|
| inbox | 38 | 100.0% |
Which ESP's emails are landing where. Sorted by spam % so problem senders surface first. Brands using one ESP for marketing and another for transactional often see very different placement profiles per ESP. Per-ESP folder data only started being captured recently — counts here may be smaller than the total above until backfill catches up.
| ESP | Emails | Placement | Inbox % | Tabs % | Spam % |
|---|---|---|---|---|---|
| Deployteq | 37 | 100.0% | 0.0% | 0.0% | |
| HubSpot | 1 | 100.0% | 0.0% | 0.0% |
Daily observations per ESP. Brands often run multiple ESPs concurrently — marketing on one, transactional on another — so this chart shows usage rather than switches.
IP addresses deployteq.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 20.49.202.3 | uk2-emailsignatures-cloud.codetwo.com |
21 | — | Check → |
| 35.157.196.176 | dmta-176.msdp1.com |
4 | — | Check → |
| 176.110.104.132 | 132-smta.msdp1.com |
2 | 1 | Check → |
| 176.110.104.100 | 100-smta.msdp1.com |
2 | — | Check → |
| 176.110.104.68 | 68-dmta.msdp1.com |
1 | — | Check → |
| 176.110.104.107 | 107-smta.msdp1.com |
1 | — | Check → |
| 52.58.141.98 | mta-027.msdp1.com |
1 | — | Check → |
| 20.58.22.103 | uk1-emailsignatures-cloud.codetwo.com |
1 | — | Check → |
| 158.247.24.254 | bid47yo.bf06x.hubspotemail.net |
1 | — | Check → |
| 176.110.104.103 | 103-smta.msdp1.com |
1 | — | Check → |
| 176.110.104.104 | 104-smta.msdp1.com |
1 | — | Check → |
| 176.110.104.134 | 134-smta.msdp1.com |
1 | — | Check → |
| 52.58.148.189 | mta-039.msdp1.com |
1 | — | Check → |
| 176.110.104.133 | 133-smta.msdp1.com |
1 | — | Check → |
| 176.110.104.90 | 90-smta.msdp1.com |
1 | 1 | Check → |