╭───────────────────────────────────────────────────────────────────────────────╮
│ example.com   0 sending services                                              │
│ 210 lookups in 0.0 s over Google DNS over HTTPS, checked 2026-10-12 01:25 UTC │
╰───────────────────────────────────────────────────────────────────────────────╯
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).

NEEDS ATTENTION
  ● The domain accepts no mail
    It publishes a null MX record, which tells senders it receives no email.
      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.                                                                   
      *._domainkey.example.com TXT v=DKIM1; p=

WHAT WAS ASKED
  example.com: 25 CNAME labels, 2 pages
    Pages: https://example.com/,                                                                    
    https://api.certspotter.com/v1/issuances?domain=example.com&include_subdomains=true&expand=dns_n
    ames                                                                                            
    CNAME labels: 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                                         

NOT RUN
  certificate transparency, crt.sh: read only with --ct (it also holds expired certificates)
