Cloudsign uses Salesforce MC for marketing email and Amazon SES for transactional/notifications. They rank #21,804 in the Tranco list of most-popular domains. Email goes out from 2 different subdomains. Their email authentication setup is solid (score 95/100).
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.
SPF / DKIM / DMARC above reflect the last 4 emails we've observed. DMARC policy is read live from DNS.
DMARC reports sent to cloudsign.jp. Policy
p=quarantine means receivers actively block or quarantine spoofed mail.
SPF alignment: 80% of observed emails use an aligned return-path (mail.cloudsign.jp); the rest use third-party paths (bounce.g.s11.pdmailservice.com) where DMARC has to rely on DKIM alignment.
DKIM alignment: all 5 observed emails sign with a domain aligned with cloudsign.jp (cloudsign.jp, b4.cloudsign.jp). DKIM authenticates the visible From — supports DMARC directly.
Delivery (last 7 days): 50% under 10 seconds, 0% over 1 minute (across 4 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.
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: cloudsign.jp, mail.cloudsign.jp, bounce.g.s11.pdmailservice.com, b4.cloudsign.jp
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 % |
|---|---|---|---|---|---|
| Salesforce MC | 1 | 100.0% | 0.0% | 0.0% | |
| Amazon SES | 4 | 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 cloudsign.jp has been observed sending from, and where their mail landed in Gmail.
| Domain | ESPs detected | Delivery (7d) |
|---|---|---|
cloudsign.jp | Amazon SES 4 | |
b4.cloudsign.jp | Salesforce MC 1 |