Age and identity checks have become a normal part of life online. A shop asks you to confirm you are an adult, a platform wants to know it really is you before paying you for a sale, a hire service checks your driving licence. They are almost always legitimate requests. It is still worth noticing when a request asks for more than it needs, or is not what it seems.
This post gathers the signs an ID check asks too much: some you will find on the check page or in the privacy notice, others you will notice in the way the request reaches you. None of these signs, on its own, means something has gone wrong. Together, they tell you whether it is time to stop and choose another route.
It is the diagnostic side of the recommendation to prove only what is asked when a site checks your age or identity. The ways copies of documents and fake verification requests are used against people are explained in the post on identity theft from ID documents.
What these signs are
In cybersecurity people talk about indicators: traces that suggest a situation deserves attention. With age and identity checks, indicators come in two kinds:
- technical, meaning information you find on the check page, in the site’s address or in the privacy notice: who runs the check, what it asks for, what it keeps;
- observable, meaning behaviour you notice in the way the request arrives: an unexpected message, a tight deadline, an unusual channel.
An indicator is not proof. It is an invitation to look more closely.
Why they matter more now that checks are multiplying
Until a few years ago an online age check was rare. Today it is common. In the UK, from 25/07/2025, sites and apps that allow pornography must have strong age checks in place, as Ofcom explains; in Italy, according to AGCOM, its rules for adult content sites have been fully in force since 12/11/2025; and the European Commission expects its age verification solution to be available across the EU by the end of 2026.
More checks means more habit of responding, and scammers count on exactly that. A message asking you to “verify your age” or “confirm your identity” seems plausible today, because it often is. That is why the signs help: not to make you suspicious of every check, but to recognise the one that asks too much.
Technical indicators
| Indicator | Where you see it | What it may mean | How much it weighs | What to do |
|---|---|---|---|---|
| For an age check you are asked for your document, front and back, plus a selfie | Check page | The method hands over your full identity when a fact would do | Medium | Look for a method that returns only a yes or a no |
| No explanation of how the check works | Check page, privacy notice | You cannot know who receives the data or how long it is kept | Medium | Ask for information before going ahead |
| The privacy notice does not say who runs the check or how long images are kept | Privacy notice | The information you need to use your rights is missing | Medium | Write to the service or choose another method |
| The page address does not match the site you are using | Address bar | It may be a fake page, or an outside provider that is not named | High | Close the page and reopen the service yourself |
| You are asked for an account password, or for card details when you are not buying anything | Check form | An age check does not need your password, and a card is a method only if the service says so: a likely theft attempt | High | Enter nothing, and change any passwords you have already entered |
| You are asked to send your document by email or chat | Service instructions | The document ends up in a channel not designed to keep it safe | Medium to high | Ask for an upload inside the site or another method |
| To confirm you are an adult you are also asked for your address, National Insurance number or document number | Check form | Data is being collected that the fact does not require | Medium | Leave optional fields empty and ask why the others are needed |
Signs you can observe yourself
| Sign | When you notice it | What it may mean | How much it weighs | What to do |
|---|---|---|---|---|
| The verification request arrives by email, text or chat, with a link | Without your having started anything | Possibly a fake message exploiting how common checks have become | High | Do not use the link; open the service from your bookmark or the app |
| The message threatens to suspend your account within hours | In the message text | Urgency is there to stop you thinking | High | Take the time to check on the official website |
| You are asked for a selfie holding your document for a simple age check | During the check | The request is out of proportion to the fact to prove | Medium to high | Ask for an alternative or give up that service |
| The check fails several times and asks for a different document each time | After the first attempt | Possibly a system error, or document harvesting | Medium | Stop and contact the service through an official channel |
| Someone calls you to “complete verification” and asks you to read out a code | On the phone | An attempted phone scam | High | Hang up and call the service back on its official number |
| A service you do not use writes about a “pending” verification | In your inbox | A generic message sent to many people | Medium | Ignore it; if in doubt, check on the official website |
| You are asked for a small payment to complete verification | At the end of the check | An age check does not usually involve a payment; if the request does not come from the service you opened, possibly harvesting card details | High | Do not pay from that page; close it and check from the service you opened yourself |
Signs in requests that come from outside
The real check is almost always inside the service you are using. Requests that come from outside deserve more attention, because of a few recurring features:
- the sender looks right, but the link goes elsewhere: the service’s name appears in the text, but the page address is different;
- the request follows a news story: after new age rules are announced, “verify before the deadline” messages become more credible;
- you are invited to download an app from a link to complete verification: real apps are downloaded from the official stores, not from a message;
- the call asks for a code that has just arrived by text: that code is for signing in or approving something, not for proving your age. The neighbouring topic of sign-in requests you did not start is covered in the post on unexpected verification requests.
In all these cases the check is the same: do not start from the message, start from the service, opened by you.
A concrete example
Helen works in an architecture practice in Milan and, in her spare time, sells the odd piece of design furniture online. The platform she uses asked her, months ago, to verify her identity so she could receive payments: Helen did it from the app, uploading her document. It is a legitimate request, because anyone handling payments needs to know whom they are paying.
One Tuesday she receives an email with the platform’s logo: “Your verification has expired. Complete verification again within 48 hours or your account will be suspended”. The button opens a page asking for her document, front and back, a selfie holding the document and, “to confirm payments”, her card number with the expiry date and the code on the back.
Helen stops. She counts three signs: the tight deadline, the link received by email, the request for card details. She closes the page, opens the platform’s app as she always does and looks for the verification section: it shows as complete, with no deadline. She reports the email to the platform and deletes it.
She entered nothing. Her real verification, meanwhile, had never expired.
What to check right away
If a request leaves you in doubt, a few checks are enough:
- Where does the request come from? If from the service you opened yourself, that is a good start; if from a message, open the service yourself and look for it there.
- What is the fact to prove? Age, your identity, an entitlement: compare the request with the fact.
- Who runs the check? Look in the privacy notice for the provider’s name and what it keeps.
- What are you being asked for? An account password is not needed to prove your age, and a code received by text is not something to read out to anyone.
- Is there a method that hands over less? Often there is, even if it is not the first button.
If you find a suspicious indicator
Stay calm: in most cases it is just an unclear check, or a fake message you have not opened. If you have already sent something, though, it is worth:
- adding nothing more and closing the page;
- noting what you sent, to which address and when;
- changing straight away, from a device you trust, any passwords you entered;
- telling your bank, if you entered card details;
- reporting the fake request to the real service.
Over the next few days, watch for sign-in alerts, transactions you do not recognise and messages in your name reported by your contacts. If you sent a document to a fake page, the recovery steps, from reporting it to asking for deletion, are in the guide on how to verify your age without oversharing.
What is not an indicator
Some situations look suspicious but are usually normal:
- a bank or payment service asking for your full document: anyone opening accounts or handling payments is required by law to know who you are;
- a short video of your face during an identity check: it is used to confirm that a real person is in front of the camera, and legitimate services explain this;
- an outside company named in the privacy notice: many sites hand the check to a specialist provider, and it is a good sign that they say so;
- being asked to retake the photo in better light: face estimates need clear images;
- a separate app opening to generate the proof of age: some systems deliberately keep the proof separate from the site;
- a new check on a site you have used for years: the rules have changed in several countries, and many services are adapting.
The rule for telling them apart is always the same: a check is normal when it asks for what the fact requires, and comes from the service you opened yourself. If in doubt, the cautious choice costs nothing: close it, reopen the service yourself and check there.
How often to check
| When | What to check |
|---|---|
| At every age or identity check | The fact to prove, who runs the check, what is being asked |
| At every message asking for verification | Whether the request also appears inside the service, opened by you |
| Once a year | The list of services you have sent a document to |
| After news of a data breach | Whether the service involved had a copy of your document |
Two important warnings
First warning: no sign is conclusive. A fake page can be identical to the real one, and a legitimate check can be poorly explained. The most reliable sign remains the simplest: always start from the service, opened by you, and ask yourself what fact you need to prove.
Second warning: checks change. Methods, rules and providers vary from country to country and from year to year. If a request seems new, look for the explanation on the service’s official website or on the pages of the authorities, such as Ofcom, the ICO or the European Commission.
How this connects to the Cyber Welfare Framework
| Pillar | What this content contributes |
|---|---|
| Awareness | Recognising that a verification request can ask for more than it needs, or not be what it seems |
| Skills | Knowing how to read the check page, the privacy notice and the address, and to tell an age check from an identity check |
| Secure Behaviour | Stopping at disproportionate requests or ones that come from outside, and always starting from the service you opened yourself |
Reference level: FL2 — Beginner. This is the level where you start noticing what a check really asks for, and asking why. To see where you stand on your other digital habits, you can take the digital resilience self-assessment.
Conclusion
The most common sign is also the simplest: a request that asks for far more than the fact to prove. Almost always it is just a poorly designed check. Sometimes it is a fake message taking advantage of how common checks have become. Either way the answer is the same: stop, reopen the service yourself and choose the method that hands over least.
Noticing is the first step. The second is making sure every check receives from you only what it needs.
Related resources
Short reads from the Resources section, for anyone who wants to focus on a single aspect:
- Online Age Verification: Prove Your Age, Share Less
- Spear Phishing: Why Scam Messages Know So Much About You
Related content
- Prove only what is asked — the recommendation this post comes from
- Identity theft from ID documents — how copies of documents are stolen and used
- How to verify your age without oversharing — the steps in priority order
- Age verification privacy risks — what gets hit
- Unexpected verification requests — the neighbouring topic of sign-in requests you did not start
Start with the first step: the Cyber Welfare Programme guides you free of charge, one recommendation at a time.




