Email infrastructure of yellowblue.io
According to Live Direct Marketing's daily DNS scan (September 7, 2026), yellowblue.io (Tranco rank #873) points its inbound MX to Amazon SES (inbound). The dataset currently contains no DMARC record for this snapshot. That is an authentication observation, not an inbox-placement result.
Last updated: .
| Mailbox provider (MX) | Amazon SES (inbound) |
|---|---|
| ESPs in SPF | none detected |
| SaaS senders in SPF | none detected |
| DMARC policy | no record |
| Tranco rank | #873 |
| Snapshot | 2026-09-07 (updated daily) |
Keep an eye on yellowblue.io
Get a first health report, then meaningful changes to SPF, DMARC, MX, sampled MX PTR and blocklists. See your domain history and run a real inbox placement test from your private watchlist.
Manage existing subscriptions →How yellowblue.io compares
Same daily dataset, three views: how its mailbox provider is trending, how strict DMARC is at its position in the list, and where its own policy sits among all DMARC publishers in the dataset.
Market share of Amazon SES (inbound)
DMARC enforced by list position
Policy maturity of all DMARC publishers
From observation to a useful check
- What was observed
- The DNS records and classifications in this snapshot.
- What it means
- MX describes inbound mail; SPF authorizes senders.
- What is unknown
- The actual sending IP, nested SPF dependencies, inbox placement and commercial relationships. MTA-STS, TLS-RPT and BIMI adoption are not measured.
- Next check
- Verify current DNS and test a real message: run an inbox placement test.
DNS records
Source: OpenINTEL / Tranco. Capture: 2026-09-07. These are answers from the measurement vantage point, not a live DNS check. TTL is the observed cache lifetime in seconds.
yellowblue.io · A — Unknown: no conclusive answer in this capture
IPv4 addresses for this name. They do not identify the mail server or prove a hosting migration.
yellowblue.io · AAAA — Unknown: no conclusive answer in this capture
IPv6 addresses for this name. An address record does not test service availability.
yellowblue.io · NS — Answer records observed
Name servers listed for the DNS zone.
Query observed at: 2026-09-07T00:22:10Z.
Response code: 0.
- yellowblue.io · NS · TTL 172800 s · 2026-09-07T00:22:10Z · AD=0
ns-102.awsdns-12.com. - yellowblue.io · NS · TTL 172800 s · 2026-09-07T00:22:10Z · AD=0
ns-1083.awsdns-07.org. - yellowblue.io · NS · TTL 172800 s · 2026-09-07T00:22:10Z · AD=0
ns-1891.awsdns-44.co.uk. - yellowblue.io · NS · TTL 172800 s · 2026-09-07T00:22:10Z · AD=0
ns-751.awsdns-29.net.
yellowblue.io · MX — Answer records observed
Servers named to receive mail. Lower preference numbers are tried first.
Query observed at: 2026-09-07T00:22:10Z.
Response code: 0.
- yellowblue.io · MX · TTL 14400 s · 2026-09-07T00:22:10Z · AD=0
10 inbound-smtp.us-east-1.amazonaws.com.
yellowblue.io · SOA — Answer records observed
Zone administration data. The serial is a version number, not a creation date or clock.
Query observed at: 2026-09-07T00:22:10Z.
Response code: 0.
- yellowblue.io · SOA · TTL 14400 s · 2026-09-07T00:22:10Z · AD=0
expire=1209600; minimum=86400; mname=ns-751.awsdns-29.net.; refresh=7200; retry=900; rname=awsdns-hostmaster.amazon.com.; serial=1
yellowblue.io · CAA — Unknown: no conclusive answer in this capture
Rules for certificate issuance. These do not show whether an existing certificate is valid.
yellowblue.io · TXT — Answer records observed
Text records can publish mail policies, domain-control challenges or other data.
Query observed at: 2026-09-07T00:22:10Z.
Response code: 0.
Domain-control verification for Google; not proof of active SaaS or mail use.
Raw TXT value
yellowblue.io · TXT · TTL 14400 s · 2026-09-07T00:22:10Z · AD=0"google-site-verification=zMGFp2emJoYgytuKdzyaVDMDe7fuu3jVRsJ4pM-QToA"
yellowblue.io · DNSKEY — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
yellowblue.io · DS — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
yellowblue.io · CDS — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
yellowblue.io · CDNSKEY — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
www.yellowblue.io · A — Unknown: no conclusive answer in this capture
IPv4 addresses for this name. They do not identify the mail server or prove a hosting migration.
www.yellowblue.io · AAAA — Unknown: no conclusive answer in this capture
IPv6 addresses for this name. An address record does not test service availability.
_dmarc.yellowblue.io · TXT — Unknown: no conclusive answer in this capture
Text records can publish mail policies, domain-control challenges or other data.
DNSSEC records are shown only when returned. An unset AD flag is not proof that a zone is unsigned. MTA-STS, TLS-RPT, BIMI and arbitrary DKIM selectors are not measured here; their absence cannot be inferred.
Recorded DNS history
Registry presence: first seen 2026-04-28; last seen 2026-09-07. These are appearances in our domain registry, not domain registration dates or earlier DNS values.
This history starts with saved RR captures. Provider market-share charts are aggregate context, not this domain’s DNS history. Dates identify observations; no continuous validity between them is implied. Equivalent RR states are combined, ignoring response TTL and capture-time changes. Up to 30 distinct RR states and 60 dated captures are retained within a per-domain byte limit.
No earlier different RR snapshot is available for comparison.
Available saved snapshots
2026-09-07 (equivalent state also recorded on 2026-09-05)
Each query below keeps its own observation date; unknown checks may retain older values.
yellowblue.io · MX
2026-09-07 — Answer records observed
- yellowblue.io · MX
10 inbound-smtp.us-east-1.amazonaws.com
yellowblue.io · NS
2026-09-07 — Answer records observed
- yellowblue.io · NS
ns-102.awsdns-12.com - yellowblue.io · NS
ns-1083.awsdns-07.org - yellowblue.io · NS
ns-1891.awsdns-44.co.uk - yellowblue.io · NS
ns-751.awsdns-29.net
yellowblue.io · SOA
2026-09-07 — Answer records observed
- yellowblue.io · SOA
expire=1209600; minimum=86400; mname=ns-751.awsdns-29.net; refresh=7200; retry=900; rname=awsdns-hostmaster.amazon.com; serial=1
yellowblue.io · TXT
2026-09-07 — Answer records observed
Domain-control verification for Google; not proof of active SaaS or mail use.
Raw TXT value
yellowblue.io · TXT"google-site-verification=zMGFp2emJoYgytuKdzyaVDMDe7fuu3jVRsJ4pM-QToA"
Changes to yellowblue.io
No entry for this domain appears in the current public change feed. The feed is a selected sample, so this does not establish that its DNS stayed unchanged.
Start monitoring to build a history from your first check, or explore observed changes across the dataset.
Modern mail security across the dataset
The required DNS labels are not queried. Adoption is unknown for this domain and for the population. Apex TXT anomalies are listed separately in the security posture report.
Reverse DNS of inbound MX hosts
These are separately dated observations of inbound MX addresses. They do not identify the actual sending IP. To assess outbound mail, check current forward and reverse DNS of the actual sending IP; FCrDNS and delivery were not measured here.
inbound-smtp.us-east-1.amazonaws.com
Partial observation: some addresses were not checked or the resolver could not determine their PTR records.
DNS attempt: 2026-09-08 06:00:52 UTC. 3 of 5 addresses queried; 3 definite address results in the saved observation.
| Observed IP | Observed PTR names | DNS observation |
|---|---|---|
3.211.210.226 | ec2-3-211-210-226.compute-1.amazonaws.com | PTR observed |
44.206.9.87 | ec2-44-206-9-87.compute-1.amazonaws.com | PTR observed |
44.210.166.32 | ec2-44-210-166-32.compute-1.amazonaws.com | PTR observed |
54.164.173.191 | — | Not checked (query limit) |
54.197.5.236 | — | Not checked (query limit) |
Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.
The observed IP 3.211.210.226 is also associated with 5 other MX hostnames. Outbound use and reputation were not measured.
Where yellowblue.io stands
The same snapshot cut by zone, by list position and by how alive the published policies are.
- At this list position the top three mailbox providers hold 60.8% of domains (Google Workspace, Microsoft 365, Unknown / Other).
- Across the dataset 25.1% of DMARC records are inert — policy does nothing and no reports are collected.
How to interpret these observations
MX identifies the observed inbound mailbox or gateway. SPF includes identify services authorised to send for the domain. DMARC shows the published authentication policy. The dataset currently contains 1 populated signal groups for this page.
Observed deliverability context: based on the available observations, this page describes DNS configuration only. It does not represent a complete audit of yellowblue.io and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does yellowblue.io use?
yellowblue.io uses Amazon SES (inbound) for inbound mail (detected from its primary MX record) as of September 7, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
Does yellowblue.io enforce DMARC?
No — yellowblue.io publishes no DMARC record at all (as of September 7, 2026).
Related domain statistics
Nearby domains in the Tranco ranking: jetbrains.com · chess.com · disqus.com · frontiersin.org
Browse provider data · Compare historical periods · Run an inbox placement test
Data: Email infrastructure of the Tranco top-1M, daily snapshot 2026-09-07, derived from OpenINTEL forward-DNS measurements. Cite with the date — records change daily.