Start with the warning, not with trust
A link from someone you met through dating can arrive as proof of a story, a booking page or a service they want you to use. If your browser has already shown a warning, the useful question is not whether you trust the person. It is what the warning is actually telling you, and what you can check without opening the link.
Stop at the warning. Do not enter a password, card number, verification code or identity document. Do not click through a warning page, accept a certificate exception, turn off your browser’s protection or install anything the link offers. None of those actions answers the question you actually have.
What each warning does and does not mean
Use this table to separate what the browser is telling you from what it is not telling you. The middle column describes the message; the last two columns are what you can reasonably do and what remains unanswered.
| What you see | What it can mean | Safe next action | Still unanswered |
|---|---|---|---|
| Red “Dangerous site” warning | Chrome may show this for phishing, malware, unwanted software or social engineering; Google recommends not visiting such a site. | Close the tab. Do not visit. Check the claimed organization through a page you find yourself. | Whether the sender knew what the link was, and whether the person is who they say they are. |
| “Your connection is not private” | Google explains this error can involve the site, the network or your device. | Do not proceed or add an exception. Try a network you control if you need to rule out your own connection, and check the service separately. | Whether the site is legitimate; the error alone does not settle that. |
| Lookalike-site warning (“Did you mean”, “Is this the right site”, “Fake site ahead”) | Google says these can flag an address that resembles a different expected site. | Compare the claimed organization’s name with the address you were sent, without opening it. Reach the organization through a route you locate independently. | Whether the resemblance is a typo, a copy or something else. |
| Secure connection, no warning | Chrome security symbols describe whether it established a secure and private connection with a site. | A secure connection still calls for care with personal information and checking the site name, per Google. | Whether the sender is honest, whether the service exists as described, and whether the request is legitimate. |
A padlock or the absence of a warning tells you about the connection, not about the person. It does not certify the organization, the offer or the story you were told. Source
So a clean-looking page is not a green light to share a card number, a code or a copy of your ID. Check the site name against the name you expected, and keep the decision about what to enter separate from the decision about what to believe.
Dangerous-site and lookalike warnings
Chrome may show a red Dangerous site warning for phishing, malware, unwanted software or social engineering; Google recommends not visiting a site with that warning. Source
That is the practical reason to close the tab rather than “just look.” If the sender’s story depends on that page, ask for the organization’s name and a public way to reach it, not another copy of the same link.
A lookalike address is worth pausing on even when the page looks polished. Compare the name you were given with the address in the message, character by character, without opening it. Then find the organization through a route you choose.
When the browser says the connection is not private
Google explains a Your connection is not private error can involve the site, network or device. Source
Because the cause can sit with the site, your network or your device, this error is not by itself proof of fraud, and it is not proof of safety either. Do not add an exception to get past it. If you want to rule out your own connection, try a network you control, but still check the claimed service through a page you locate independently rather than through the sent link.
What a security check can and cannot tell you
Google’s Site Status diagnostic checks whether a site currently contains content that Safe Browsing has determined to be dangerous. That is a narrower question than “is this organization real” or “is this person honest.” A status result is about detected dangerous content, not about the sender’s intentions or the truth of their story. Google Safe Browsing.
Check the claim, not the link
Once you have stopped, the safer route is to verify the organization or service through a page you find yourself, not through the link you were sent. Practical steps:
- Write down the organization’s name as the sender stated it, plus any headline or domain text visible in a screenshot they sent.
- Find the organization’s own public page through a search you run, and compare the name and the service described there with what you were told.
- If the sender says a booking, fee or verification is required, check that requirement on the organization’s own page before acting on the message.
- Keep the conversation going, but ask for the public name of the service rather than another link.
- If money has already been requested by someone you have not met in person, pause the payment and talk to someone you trust.
FTC advises never sending money or gifts to a love interest not met in person, speaking to someone trusted, and reporting suspected romance scams to the platform and FTC. Source
That advice is a stop point about money, not a finding about this particular person. A warning alone does not establish the dating contact’s intent, and a missing warning does not clear them.
If the only screenshot is one they sent
A screenshot alone does not verify the sending device, capture time or authenticity. It does not establish what your own browser or the current site would show. If you want to examine wording in a screenshot you own or have permission to review, keep private URL tokens, messages and account details out of it, and use only non-sensitive text such as a public service name or headline.
For the separate step of reading text from a screenshot before searching public posts, see checking screenshot text before searching public posts.
Using TraceSeek after you have stopped
The App is a way to organize public leads, not a security scanner. It does not test links, detect malware, approve payments or operate platform controls, and the website itself does not accept uploads or perform searches.
Once you have an already visible, non-sensitive public service name, headline or domain text, the App’s image-text search can use that wording from an authorized screenshot as a public search clue. Its deep search can broaden public-source retrieval about the claim. Keep live login or payment links, private messages and account details out of the App; do not treat it as a check on whether a URL is safe.
TraceSeek returns public leads and organizes accessible sources. It does not certify identity or confirm a relationship allegation. If you want to try that step, you can start from the App page.
If the specific request is an external card-verification link before you have met, the separate guide on a dating match’s verification link before entering your card covers that situation.
What is still open after you stop
Stopping avoids further interaction; it does not undo earlier downloads, payments or disclosures. It does not resolve whether the sender is who they claim, whether the service is real, or whether the story is true. Those questions need independent public information about the organization and, where money is involved, the pause-and-talk-to-someone step above. Keep the distinction clear: the browser warning is about the connection or the site, and your judgment about the person is a separate decision made with better information.