Ironcitybham uses SparkPost as their primary email service provider. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
Non-ESP tools detected in this brand's emails. Independent of who sends — a brand can use any combination.
| HTML builder |
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 8 emails we've observed. DMARC policy is read live from DNS.
DMARC published as p=none with no rua= reporting — monitor-only, and the sender isn't collecting reports either.
DKIM alignment: all 11 observed emails sign with a domain aligned with ironcitybham.com (mail.ironcitybham.com). DKIM authenticates the visible From — supports DMARC directly.
TLS: 0% TLS 1.3, 100% TLS 1.2 (across 11 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).
None — only the primary ESP(s) shown aboveESPs 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.
No additional ESPs authorized in the brand's SPF beyond the confirmed senders above.
Probed: ironcitybham.com, mail.ironcitybham.com
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 | 11 | 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 % |
|---|---|---|---|---|---|
| SparkPost | 11 | 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 ironcitybham.com has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Placement | Reputation |
|---|---|---|---|---|
| 168.203.37.212 | mta-203-37-212.sparkpostmail.com |
6 | 6 | Check → |
| 147.253.215.13 | mta-253-215-13.sparkpostmail.com |
2 | 1 | Check → |
| 192.174.90.14 | mta-90-14.sparkpostmail.com |
1 | — | Check → |
| 192.174.90.11 | mta-90-11.sparkpostmail.com |
1 | — | Check → |
| 168.203.37.74 | mta-203-37-74.sparkpostmail.com |
1 | 1 | Check → |
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail.ironcitybham.com | SparkPost 11 |