No sending service shows in DNS for example.com: a null MX that says it accepts no mail, no sender in SPF, and a wildcard that answers every DKIM name.

Not checked: the crt.sh certificate log (read only with --ct).

Good to know

Nothing to change here. These explain what the map shows.

The domain accepts no mail. It publishes a null MX record, which tells senders it receives no email.
Records
- example.com MX 0
Every name under _domainkey.example.com answers with a key. A wildcard record makes every selector look published, so keys there say nothing about which services sign for the domain.
Records
- *._domainkey.example.com TXT v=DKIM1; p=

How this was checked

210 lookups at 1 name · 1 thing not checked

Not checked

certificate transparency, crt.sh. Read only with --ct (it also holds expired certificates).

What was asked

210 lookups at 1 name

At example.com: 25 service record names, 2 web pages.

Names asked

example.com

Pages (2): https://example.com/, https://api.certspotter.com/v1/issuances?domain=example.com&include_subdomains=true&expand=dns_names
CNAME labels (25): bounce, bounces, em, email, mail, send, mta, rp, pm-bounces, links, link, click, track, tracking, url, go, autodiscover, cf-bounce, eversrv, fwdkim1, bnc3, bounces.cloud.em, bounces.cloud2.em, outbound.intercom, atlassian-bounces