Android SMS (mmssms.db)
Android Telephony provider stores SMS and MMS in a single SQLite database accessible via content providers, often recoverable even after app reinstall.
Where to find it
Default filesystem paths and registry locations. Collect these with your preferred live-response or disk-image tooling.
- $/data/data/com.android.providers.telephony/databases/mmssms.db
Forensic significance
Common scenarios in which this artifact becomes decisive evidence.
- Threatening or harassing message content
- 2FA bypass investigation — SMS interception
- Smishing — link delivery to victim
Tools that parse it
unJaena AI and other DFIR tools commonly used to extract evidence from this artifact.
Related artifacts
Android Call Log
contacts2.db logs every incoming, outgoing, missed, and rejected call with duration, contact, SIM slot, and call type including voicemail.
iOS SMS / iMessage (sms.db)
iOS stores SMS, MMS, and iMessage conversations in a single SQLite database including timestamps, read receipts, attachments, and reply threading.
iOS Call History
CallHistory.storedata logs every cellular, VoIP, FaceTime, and third-party call (WhatsApp, KakaoTalk) with duration, direction, and contact information.
KakaoTalk iOS
Korea's dominant messenger. iOS client stores chatrooms, messages, contacts, and attachment metadata in SQLite databases inside the app sandbox.
Stop parsing artifacts by hand
unJaena AI ingests disk images, live-response output, and mobile backups, then automatically correlates every artifact on this page — and 200+ more — into an investigator-ready timeline.
Try unJaena AI →