📮 Physical Address
A physical or mailing address tied to a person, company, or registered entity.
Identity
Sources
3
3 no-auth
Disciplines
2
that use it
Mission domains
6
reach
Workbench
—
native tool
🔗 Analyst pivots
🔌 Sources that yield Physical Address (3)
| Source | Category | Auth | Format | |
|---|---|---|---|---|
| GLEIF LEI + OpenCorporates Legal-entity & corporate registry intelligence. | CORPINT | NONE | json | home↗ api↗ |
| Identity / National-ID references Identity attribute validation references. | IDENT | NONE | html | home↗ |
| Land Registry / Property Records Real-property ownership & transactions. | CORPINT | NONE | json | home↗ api↗ |
🧭 Disciplines
🎯 Mission Domains
🔍 Lookup
🔄 Live Datasets & APIs (2 key-free · ingestible)
| Dataset / API | Format | Endpoint | |
|---|---|---|---|
| GLEIF LEI + OpenCorporates | json | https://api.gleif.org/api/v1/ | collect |
| Land Registry / Property Records | json | https://landregistry.data.gov.uk/ | collect |
📜 Playbook — Physical Address exploitation
- Direction — frame the requirement for Physical Address: what decision does this support, by when?
- Collection — pull the 3 mapped sources (3 free) and the native workbench; capture provenance and observe OPSEC.
- Processing — normalize, de-duplicate and enrich the collected data.
- Analysis — correlate against local holdings; apply ACH; assign confidence.
- Dissemination — open a case, draft a report, share via STIX/MISP.
- Feedback — set an alert rule / watchlist to monitor for change.
⚡ AI Skills & Automation
Automate unattended via the cron pipeline (collect → ingest → resolve → enrich → score → alert).
🧩 Advanced Capabilities
✨ Enrichment pathways
🎫 Physical Address
A physical address is a structured geographic location (street, locality, region, postal code, country) tied to residence, business, or registration records. It grounds digital identities in the physical world, enabling co-location analysis, corporate-registration linkage, and pattern-of-life reconstruction.
Format: Unstructured or structured postal address; normalize/geocode to lat-long and standardized components (libpostal, ISO-3166 country, postal-code regex per country). Validate against authoritative address datasets.
📡 How it is collected
- Corporate registries and business filings
- Property and land records
- WHOIS registrant addresses
- Breach and delivery/marketing datasets
- Court filings and legal notices
- Geocoded social/EXIF metadata
📚 Enrichment & validation sources
🔗 Pivot to
🧩 Analysis & hunting techniques
- Address normalization and geocoding
- Co-location clustering (shared registered addresses)
- Mass-registration / virtual-office detection
- Property-ownership chain analysis
- Reverse-geocoding of EXIF/geo metadata
- Satellite/street-level imagery verification
- Corporate-registry address correlation
- Postal-format validation per jurisdiction
🔧 Tools
- libpostal
- Nominatim
- QGIS
- OpenRefine
- Maltego
- OSM Overpass Turbo
- Google Earth (reference)
- OpenCorporates API
⚡ Workbench actions
- Normalize and geocode address
- Detect shared/virtual-office registrations
- Map co-located entities
- Pull property/registry ownership
- Verify with satellite/street imagery
- Reverse-geocode media metadata
- Cluster registrants by address
- Plot on country dashboard map
📊 Dashboard KPIs
Geocode confidence scoreCo-located entity countVirtual-office / mass-registration flagLinked persons/companiesRegistry record count
📂 Open
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Explore related tools below
- Automate recurring work via cron