Google Workspace MX records today point at smtp.google.com, at the priority shown above. Many working domains still publish older values that start with aspmx, and Google still supports them. Paste any address at your domain to see which form it publishes, and whether another server takes the mail first.
Only the domain is sent, to Cloudflare's public DNS resolver. The address stays on this page, and nothing is stored.
How to read the result
If the map names Google Workspace, your mail reaches Google, in either form. If it names a security gateway, a filtering service takes the mail first. Google may sit behind it, but DNS cannot show that.
If it names Microsoft 365, another host, or none at all, mail to the domain is not reaching Google. Senders try the host with the lowest preference number first, as RFC 5321, the SMTP standard, sets out, so that host is the one that counts.
A domain with no MX record at all is usually new. Mail to it will most likely fail, so fix that before you hand out the address.
What to do next
Do not change a working MX record to fix a deliverability problem. MX records decide where mail to your domain lands, replies included, not whether receivers trust the mail you send.
That trust rests on SPF, DKIM and DMARC. The SPF record lookup shows each sender your SPF record allows.
Checking a list of prospects rather than your own domain? The bulk MX lookup page covers what each result means for a send.