California DCA Snapshot Checksums, Dates, Record Totals and Limits

Direct answer and scope

The evidence records two DCA files obtained on August 25, 2026, with a file update date of August 1, 2026. Funeral_Data00.xls contains 6,137 records and has the supplied SHA-256 value 62f35460f34dd8748672f889839c03dde187891922d0837f08b615b4bcf3be50. Cemetery_Data00.xls contains 6,688 records and has the supplied SHA-256 value 20b784291214b01de0670e242d36971c050b5a0be481f87dcce8f900a0ce47a4.

These values provide provenance for records derived from the archived files: which files were used, when the files were updated, when the snapshot was obtained, how many records each file contained, and the recorded checksum for each file. The archive should not be described as a live DCA license view.

The underlying public dataset supplies administrative fields and displayed status. The documented fields include license type, license number, an individual or organization indicator, public address of record, expiration date, and license status. A public address of record is not proof of a service location, and these fields do not establish service availability, quality, ownership links, or relationships among separately licensed entities.

How to use the supplied evidence

Use the filename, update date, obtained date, record total, and checksum together as the provenance record for the archived source. The filename distinguishes the funeral file from the cemetery file; the record total describes the number of records reported in that file; and the checksum is the supplied identifier for the archived file bytes.

Use the DCA dataset fields only for the administrative details they display. For a record connected to a matched entity, preserve the license type, license number, individual or organization indicator, public address of record, expiration date, and displayed license status as separate fields rather than converting them into broader descriptions.

A same-name result is not a confirmed match without the license number and license type. Current verification for each involved entity should be recorded separately and should state the exact license type, exact license number, displayed status, official source, and verification date. Status can change, so the verification date belongs with the result.

The DCA lookup can also be used to verify available disciplinary or public documents. Absence from one search is not proof of a clean record, and a displayed status should not be treated as a quality badge or as DCA approval of an advertiser.

Decision framework

First, identify the relevant archived file. Use Funeral_Data00.xls for the funeral records described by that filename and Cemetery_Data00.xls for the cemetery records described by that filename. Keep the two record totals and checksums attached to their respective files.

Next, compare the entity’s identifying information with the administrative fields in the sourced record. Treat a name as a starting point rather than a confirmed match. The license number and license type are required to distinguish a matched entity from a same-name result.

Then, separate snapshot provenance from current verification. The August 2026 archive documents what was obtained from files updated August 1, 2026; it does not replace a current DCA lookup. For the matched entity, record the exact license type, license number, displayed status, official source, and verification date.

Finally, keep the meaning of the result narrow. A displayed status is an administrative record field, not a rating, quality finding, service-availability statement, ownership link, or endorsement. Paid placement is separate from DCA-derived directory status and cannot change the source record or the editorial status filter.

Evidence limits and unresolved questions

The snapshot limitation is exact: it is an immutable snapshot rather than a live DCA view, and the checksums do not prove that every source record is current, active, complete, or correct after August 1, 2026. The record totals and checksum values should therefore remain tied to the archived files and their dates.

DCA describes the public information files as automatically refreshed at the beginning of each month. That refresh practice does not make the files real-time. A later status, later record change, or later correction is unresolved unless supported by a separately dated current verification.

The supplied fields also leave certain questions unresolved. A public address of record does not establish a service location. The dataset does not establish service availability, quality, ownership links, or relationships among separately licensed entities. A displayed Active status is not a quality badge, and the public dataset does not constitute an endorsement.

For a matched entity, the unresolved points should be stated rather than filled with assumptions: whether the current displayed status has changed since the snapshot, whether the number and type match the intended entity, and what current official record and verification date support the result.

Questions people ask

The provenance values identify the two archived DCA files, their August 1, 2026 update date, the August 25, 2026 snapshot date, each file’s record total, and each file’s supplied SHA-256 value. These values describe the archive used for the sourced records.

The August 2026 snapshot is not a live DCA view. It is an immutable snapshot of files updated August 1, 2026. DCA describes its public information files as automatically refreshed at the beginning of each month, so the files are monthly rather than real-time.

The checksums do not establish that every source record is current, active, complete, or correct after August 1, 2026. They identify the archived file bytes but do not answer whether a particular entity’s status later changed.

DCA’s current-license lookup is the separate verification route for a matched entity. Record the exact license type, license number, displayed status, official source, and verification date for each involved entity separately. A same-name result is not confirmed without the number and type, and absence from one search is not proof of a clean record.

Evidence behind this page

Each point below is restricted to what the cited primary source supports. Administrative listing status is not a quality endorsement.