Gmail's Mailed by and Signed by lines and its unauthenticated-sender banner describe how a sending domain was authorized or signed. They do not confirm who a person is, whether a dating claim is honest, or whether a message is safe. Treat an authentication pass as limited technical information, and a failure as a reason to slow down rather than proof of fraud. For any unexpected request for money, codes, or account access, verify through a contact route you already know, and keep full private headers out of third-party tools.
Find public social profile clues with our TraceSeek app.
What Gmail's authentication lines actually show
When you open a message's details in Gmail, you may see lines such as Mailed by and Signed by, along with a warning when a sender is unauthenticated. These lines concern the sending domain: whether it was authorized to send and whether a signature is present. They are checks on mail infrastructure, not on a romantic sender's identity or on whether the content of the message is true. Gmail itself notes that unauthenticated messages are not necessarily spam, and that even spammers can pass these checks. Read the lines as one small technical signal among many, not a verdict. [Gmail Help: message authentication]
- Open the message details only for your own review; do not forward full private headers to strangers or unknown websites.
A pass is not trust, and a failure is not guilt
The common mistake runs in both directions. A message that shows Mailed by and Signed by lines can still be a scam from a domain set up for that purpose, because authentication only speaks to sending authorization and signatures. A message that fails those checks may come from a misconfigured but legitimate sender. Neither outcome tells you whether the person writing is who they claim, whether a dating story is real, or whether a request is safe. Keep the observation separate from the decision: the technical line informs caution, while your decision should rest on independent verification.
| observation | limit | next step |
|---|---|---|
| Mailed by / Signed by lines appear | Shows sending-domain authorization only, not a person's identity or intent | Continue to an independent verification route before acting on any request |
| Unauthenticated-sender warning appears | Does not by itself prove fraud or spam | Pause, avoid replying to the demand, and verify through a known contact |
| Message looks polished and passes checks | Scammers can authenticate mail too | Judge the request, not the polish or the passing line |
Handle the request before debating the sender
If a message from a dating context asks for money, login codes, account access, gift cards, or identity documents, the protective action comes first. Do not reply to the suspicious demand, and do not use contact details supplied inside that message. Instead reach the person or provider through a phone number, app, or website you already knew before the message arrived. If you have already shared credentials, change the affected password and turn on multi-factor authentication where offered. These steps limit harm while you work out what happened, and they do not require you to decide yet whether the sender is dishonest. [FTC: How To Recognize and Avoid Phishing Scams]
- Do not reply to the demand or use contact details from the message itself.
- Change any password you entered and enable multi-factor authentication on that account.
- Reach the person or provider through a route you already trusted.
Keeping private headers away from third-party tools
It is tempting to paste a full email into a free header-checking site for a quick verdict. That passes along private content, addresses, and routing data to an unknown operator, and the result still would not establish who the sender is. If you want to inspect the message, keep it inside the mail interface you already use and read the visible lines there. If a tool or a person asks for the complete raw message, treat that as an access boundary: decline and stop. Authentication output, however detailed, does not substitute for verifying a request with someone you independently know. [Gmail Help: message authentication]
A worked example, clearly hypothetical
Suppose a dating match sends a message that appears properly authenticated and asks you to confirm a payment for a shared trip using a link in the same thread. The passing authentication lines tell you the sending domain was authorized to send; they say nothing about whether the trip or the person is real. The safer path is to skip the link, contact the person through a channel you already have, and describe the request plainly. If you cannot find an independent route, do not send money on the strength of the email alone. If instead the message carries an unauthenticated warning, that is an additional reason to pause, not a conclusion that the match is fraudulent. [Gmail Help: message authentication]
- Write down what the message asks for before you decide anything.
- Use a previously known contact route to confirm the request.
- Decline to act while verification is unavailable, and say so plainly.
If the control or information is unavailable
Sometimes the details view does not show the lines you hoped to read, or the banner is absent, or you cannot find an independent contact route. Record that the information is unavailable and stop at the access boundary rather than guessing. Ask the person, through a route you trust, for a current voluntary link or an alternative way to confirm. Do not treat a missing badge, an absent warning, or a quiet message as a sign of safety or of guilt. A gap in what you can see is simply a gap. [FTC: How To Recognize and Avoid Phishing Scams]
Returning to the conversation calmly
Once any account or money concern is handled, you can go back to the conversation without accusing anyone. Ask a plain, specific question about why the request was made and how you could confirm it through a route you both know. Keep in mind that public profile details, a matching photo, or a verified-looking status are not proof of identity or intent. Your aim is a practical decision about what to do next, not a ruling on the other person's character. If the person resists independent confirmation, that resistance is useful information for your own decision. [Gmail Help: message authentication]
A couple more questions
Does a message that passes Gmail's Mailed by and Signed by checks mean the dating sender is genuine?
No. Those lines concern the sending domain's authorization and signature, not the sender's identity, honesty, or whether a dating claim is true. Spammers can pass these checks too, so treat a pass as a small technical signal and verify any request independently.
Does an unauthenticated-sender warning mean the message is definitely fraud?
No. Gmail notes that unauthenticated messages are not necessarily spam, and legitimate senders can be misconfigured. A warning is a reason to slow down and verify through a known contact, not a conclusion about the sender's intent.
How should I confirm an unexpected money or code request from a dating match?
Do not reply to the demand or use details from the message. Reach the person or provider through a phone number, app, or website you already knew, and if you shared credentials, change the password and enable multi-factor authentication. If you cannot verify, do not act.
Can I paste the full email headers into an online checker?
Better not. A full raw message contains private content and routing details, and an unknown tool's verdict would still not confirm a person's identity. Read the visible lines in your own mail interface, and decline requests for the complete raw message.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.