Where does Android show what a tag contains?
It does not, in general. Android acts on the content rather than showing it, so a tag with a web address opens the address, from Android 17 after an open link notification, and the record itself is never displayed. Seeing what is actually on a tag, including its technical data, needs a tool built for that.
It acts rather than displays
The system reads a tag to decide what to do, not to report to you. A web address opens, a number offers to dial, and in neither case are you shown the record.
So the ordinary tap experience gives you the outcome and hides the cause, which is fine for a user and unhelpful for anyone diagnosing a tag.
A text record is the exception. Text has no action attached, so it is displayed, which is why people sometimes think a tag is showing its content when in fact its content is text.
What you do see
The browser address bar after a tag opens a page, which shows the address as the system resolved it.
A chooser, which tells you the content matched more than one application.
A notification or a brief message on some devices, which varies by manufacturer and is not something to rely on. From Android 17, a web link adds one that belongs to the platform: the NFC basics guide documents an open link notification that has to be acted on before the page opens.
None of that tells you the record type, the free space, the tag type or whether the tag is locked, which are the four things a diagnosis usually needs.
What a reading tool adds
The record list with the type of each, which is what separates a working tag from one that is read and ignored.
The technical data: the chip, the NFC Forum tag type, the identifier, the free space, and whether the tag is writable.
The ability to read without acting, so a tag can be examined without being opened. That matters when you do not know where a tag points.
This is the difference between knowing what happened and guessing, and it is why a reading tool belongs in any deployment kit.
Why this matters for a deployment
Verification means comparing what is on the tag against what you intended, and the system view cannot do that.
A tag whose content is correct and whose record type is wrong passes a casual look and fails for every visitor.
Reading each tag back after writing, with a tool that shows types, is the check that catches it.
And when someone reports a tag misbehaving, reading it is the first useful step. Everything else is inference.
Frequently asked questions
Why does my tag open a page instead of showing the content?
Because a web address record carries an action, and the system performs it. Only a reading tool shows you the record itself.
Can I see a tag's content without opening it?
Yes, with a tool that reads and reports rather than acting. That is also the safe way to examine a tag you do not trust.
Why is text displayed and a URL not?
Text has no action attached, so displaying it is the only sensible outcome. An address has an obvious action and the system takes it.
Does iOS show more?
It shows a notification in the background path, which names the destination rather than the record. Examining a tag properly still needs a tool.