NFC EVIDENCE LAB · V0.5
Four tags.
One test.
Three white cards and a blue fob. A read is not proof of a distinct device. This lab grades the evidence instead of counting taps as verified cards.
White card 1
Place this card against the back of your phone.
Ready. Enable NFC and open in Chrome on Android.
FALLBACK · NFC TOOLS
Record card result
Scan the selected card using NFC Tools → READ, return here and select the chip type shown. No serial numbers or memory dumps.
Scan results
0 observationsA previously exported privacy-safe report can be analyzed without rescanning.
Diagnostic limitation: four NDEF events do not prove four different physical tags. Reader-reported IDs are not cryptographic authentication.
04B / EVIDENCE FINDINGS
What the device scans actually show
05 / LOCK-SIDE CORRELATION
Compare against the lock
Hotel locks are normally NFC readers, not NDEF tags. A phone scan cannot recover the lock's expected credential. Record only visible model information and manufacturer-documented reader technology; no hotel door interaction is performed.
This is a compatibility hypothesis, not evidence of an unlock, successful authentication, or a vulnerability. No lock commands, card cloning, RF capture or key extraction.
06 / DOOR ENTRY ANALYTICS
Correlate actual access events
A phone tap cannot extract history from a hotel lock. Use the property's authorized, anonymized audit export, or run a fully synthetic demonstration here. No external upload.
Audit coverage: unknown. A device scan cannot establish whether a hotel lock was accessed.
Local-only JSON format: privacySafe: true, events: [...] with pseudonymous credential references. The parser rejects unsupported fields and does not send data anywhere.
What this scan can (and can't) identify
Reads NDEF record types from compatible NFC tags only. MIFARE Classic without NDEF may not scan through the browser. Neither the tag's protected sectors nor a lock's expected access codes can be inspected from this page. For an authorized standalone lock, record its visible manufacturer/model and use vendor-approved diagnostics.
Nothing is written to the cards. The app keeps observations only in current page memory. Exported results omit NFC serial numbers, tag contents, keys, and personal identifiers.