Fiscal uses Beehiiv for marketing email and Amazon SES for transactional/notifications. They rank #149,851 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is good (score 73/100). Missing: DMARC enforcement.
Amazon SESAuthentication 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.
DMARC reports sent to cloudflare.net. Policy
p=none is monitor-only — receivers won't act on spoofing yet.
SPF alignment: 20% of observed emails use an aligned return-path (send.notifications.fiscal.ai); the rest use third-party paths (tinyseed.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 3 observed emails sign with a domain aligned with fiscal.ai (mail.fiscal.ai, notifications.fiscal.ai). DKIM authenticates the visible From — supports DMARC directly.
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.
"Observed" pills mean we detected emails from these ESPs, but they don't appear in any SPF record we probed. They may still be properly authorized — sending infrastructure can live on subdomains we haven't seen yet, or use IP-listing instead of include: directives.
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: fiscal.ai, tinyseed.com, send.notifications.fiscal.ai, mail.fiscal.ai, notifications.fiscal.ai
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 | 5 | 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 % |
|---|---|---|---|---|---|
| Beehiiv | 4 | 100.0% | 0.0% | 0.0% | |
| Amazon SES | 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 fiscal.ai has been observed sending from, and where their mail landed in Gmail.
| IP | Hostname | Obs | Reputation |
|---|---|---|---|
| 54.240.9.36 | a9-36.smtp-out.amazonses.com |
1 | Check → |
Per-IP inbox / promotions / spam is being collected and will appear here as new emails are observed.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
mail.fiscal.ai | Beehiiv 4 | |
notifications.fiscal.ai | Amazon SES 1 |