MRX Learning Center
Culberson CAD 2026 Certified Roll Format Boundary Source Index
Preserve four displayed certified-roll link relationships and safe response-header observations without opening or comparing the files.
Direct answer for mineral owners
Start at the current official Culberson CAD Data and Records page and preserve the four separately displayed 2026 certified-roll link relationships. A safe header-only check can record an endpoint family, HTTP status, content type, and content length before cancelling the body. Those facts identify four responses at one retrieval time; they do not prove that the files contain equivalent, complete, accurate, current, legally certified, or owner-applicable records.
Key takeaways for mineral owners
- Preserve the official publisher page and each exact displayed endpoint as separate source objects because the page relationship and endpoint response prove different facts.
- The four displayed links use two document endpoints, one spreadsheet-download endpoint, and one archive-download endpoint; the differing endpoint families do not prove content equivalence or completeness.
- HTTP 200, content type, and content length are response-header observations only, not validation of a file body, record, row, value, classification, or legal status.
- Do not download, open, preview, extract, sample, search, compare, normalize, or summarize any file body in this public source index.
- Keep the adjacent mineral-ZIP container record separate; it owns complete-file identity and generic central-directory metadata for its recorded archive retrieval.
- Stop before personal data, record content, matching, appraisal, tax, protest, legal, valuation, offer, or sale work.
Format-boundary notice. This page identifies the current official Culberson County Appraisal District Data and Records page and four displayed 2026 certified-roll link relationships. It preserves labels, exact endpoints, endpoint families, retrieval date, and safely observable response headers only. It does not download, open, preview, extract, sample, search, compare, normalize, or summarize any file body. It does not expose a name, account, address, property, row, value, or classification, and it does not decide appraisal, tax, protest, legal, valuation, offer, or sale questions. MRX provides educational information and resources only and does not buy mineral rights.
The current Culberson CAD 2026 certified roll formats appear as four separate links on the district’s Data and Records page. A careful source index should preserve that publisher-page relationship before it records anything about an endpoint.
The four links do not form a ready-made comparison dataset. Two use a document-delivery endpoint, one uses a spreadsheet-download endpoint, and one uses an archive-download endpoint. Those differences help identify the link boundary. They do not establish what the files contain or whether their records match.
Use only source-recorded, not-displayed, source-conflict, controlled-record-stop, or authorized-human-stop. These labels describe document-control status. They do not mean equivalent, complete, accurate, current, legally certified, applicable, appraised, taxable, protestable, valuable, accepted, or controlling.
Start with the official publisher page
Begin at the Culberson CAD Data and Records page. During the recorded 2026-08-27 review, the 2026 certified-roll section displayed four sibling links:
Real and Personal Geo PDFReal and Personal Alpha PDFReal and Personal ExcelCertified Mineral Appraisal Roll ZIP
Preserve the publisher-page URL, displayed section context, each label, and each exact href as separate observations. A copied endpoint without its publisher-page relationship does not by itself show that the district still displays it under the same label. Conversely, a displayed label does not prove that the endpoint body is valid, complete, accurate, or suitable for any purpose.
The official district home page and Texas Comptroller Culberson County directory provide district-site context. They do not validate a certified-roll file. Texas Tax Code Chapter 25 and Chapter 26 provide statutory provenance only. This page does not interpret those chapters or apply them to a file, property, account, owner, appraisal, notice, protest, or tax.
Keep the four exact endpoints separate
The two displayed PDF links use Forms/GetDocument. The spreadsheet link uses Forms/ExcelDownload. The mineral archive link uses Forms/ZipFileDownload. Preserve each complete query string; do not shorten it into an invented permanent identifier.
| Displayed link | Endpoint family | Safely observed response type | Public-index limit |
|---|---|---|---|
| Real and Personal Geo PDF | Forms/GetDocument | application/pdf | Label, exact endpoint, and response headers only |
| Real and Personal Alpha PDF | Forms/GetDocument | application/pdf | Label, exact endpoint, and response headers only |
| Real and Personal Excel | Forms/ExcelDownload | application/vnd.ms-excel | Label, exact endpoint, and response headers only |
| Certified Mineral Appraisal Roll ZIP | Forms/ZipFileDownload | application/zip | Label, exact endpoint, and response headers only |
The exact Geo PDF endpoint and Alpha PDF endpoint remain separate source objects. A shared endpoint family does not prove that the two PDFs contain the same records in a different order.
The exact Excel endpoint uses a separate download family and responded with an Excel MIME label. The filename ending and response label do not authorize a header, row, field, cell, or record inspection.
The exact mineral ZIP endpoint is adjacent to, but not merged with, the three Real and Personal links. The mineral ZIP source-control record owns a different job: its recorded archive container, complete-file identity, and generic central-directory metadata. This article does not repeat those facts.
Record response headers without consuming the body
A header-only check can request an endpoint, preserve the response status and selected headers, and cancel the response body immediately. It should not retain the response, compute a file hash, generate a preview, inspect a page, read a spreadsheet cell, list an archive member, or sample content.
The recorded 2026-08-27 check observed:
| Displayed link | HTTP | Content type | Content length |
|---|---|---|---|
| Real and Personal Geo PDF | 200 | application/pdf | 5,839,594 bytes |
| Real and Personal Alpha PDF | 200 | application/pdf | 5,871,490 bytes |
| Real and Personal Excel | 200 | application/vnd.ms-excel | 5,231,474 bytes |
| Certified Mineral Appraisal Roll ZIP | 200 | application/zip | 7,211,706 bytes |
These are response observations at one retrieval time. HTTP 200 means the server returned a successful response. A content type is a response header. A content length is a stated byte length. None proves that the body is uncorrupted, accurate, complete, current, legally certified, applicable to a particular interest, or consistent with another response.
Do not compare the lengths to infer row counts, omitted records, extra fields, geographic organization, alphabetic organization, compression efficiency, mineral coverage, or data quality. Different lengths can have many explanations, and this public index investigates none of them.
Do not turn format labels into equivalence claims
Geo, Alpha, Excel, and ZIP are displayed link labels or filename components in the recorded publisher relationship. They are not a verified schema. This page does not define what Geo or Alpha means inside either PDF. It does not state whether the spreadsheet contains the same fields or records as a PDF. It does not state whether the ZIP overlaps, supplements, or differs from the other three links.
Keep the distinction explicit:
| Permitted source observation | Conclusion this page does not make |
|---|---|
| Four sibling links appear in one publisher section | The files are four equivalent versions of one dataset |
Two responses use application/pdf | The PDFs contain matching pages, rows, or classifications |
| One response uses an Excel MIME label | A spreadsheet header or row is known or safe to expose |
One response uses application/zip | Its members are known from this index or match another file |
| All four returned HTTP 200 | All four bodies are valid, complete, accurate, or legally effective |
| The publisher uses the word Certified | A property record is correct, current, applicable, or controlling |
Any proposed comparison requires an authorized workflow with a defined purpose, lawful access, minimum-necessary data, source-version control, schema review, privacy controls, and qualified appraisal, legal, or tax review where appropriate. This reusable public article supplies none of that workflow.
Do not expose record content
The boundary applies even to content that looks harmless. Do not display the first page of a PDF. Do not quote a spreadsheet header. Do not list an archive member. Do not reveal a single name, account, address, identifier, legal description, property fact, owner fact, value, classification, appraisal result, tax amount, notice fact, protest detail, or row count.
Do not use an endpoint filename to infer a property’s location, owner, classification, value, or appraisal treatment. Do not combine the four links with an appraisal search, ownership record, lease, regulatory filing, production record, tax bill, notice, protest record, offer, or owner-supplied document.
A request for one sample row is still file-body access. A request to check whether one owner appears is a personal-data and matching task. A request to identify which format is best for a protest, tax review, valuation, or sale is individualized professional or transaction work. Each request falls outside this public index.
Use the five document-control states literally
Source-recorded
Source-recorded means the official publisher-page relationship, displayed label, exact endpoint, endpoint family, retrieval date, HTTP status, content type, or content length was captured during the recorded review. It says nothing about the body, records, equivalence, completeness, accuracy, currency, legal status, appraisal, tax, value, or owner result.
Not-displayed
Not-displayed means a defined label or relationship was not found on the specific publisher page during the recorded review. It does not prove that an endpoint never existed, was removed intentionally, should appear, is required, or has legal, appraisal, tax, or valuation significance.
Source-conflict
Source-conflict means a later publisher page or response displays a different label, endpoint, endpoint family, status, content type, or content length. Preserve each observation separately. Do not merge endpoints, infer why a response changed, choose a controlling file, or transfer content assumptions among formats.
Controlled-record-stop
Use controlled-record-stop when the next step would consume a file body; inspect a page, header, row, field, cell, or archive member; access personal or private data; search a property or account; match another source; or expose record content. The label identifies a boundary. It does not authorize access.
Authorized-human-stop
Use authorized-human-stop before schema comparison, equivalence testing, completeness or accuracy review, legal-certification analysis, property or account interpretation, appraisal judgment, protest strategy, tax position, legal interpretation, valuation, representation, contact, submission, payment, offer analysis, or sale advice.
The public workflow ends at either stop. It does not open credentials, access a file body, collect data, search an account, contact an office, upload a record, file a submission, make a payment, negotiate, or promise a result.
Handle publisher or endpoint drift without merging observations
A later review may find a changed label, href, filename, endpoint family, status, content type, content length, section heading, or displayed year. Treat that as source drift rather than an instruction to replace evidence silently.
- preserve the live publisher-page URL and retrieval time;
- preserve each exact current displayed label and href;
- preserve the earlier source-record observation separately;
- record the exact header-level difference;
- mark
source-conflict; - cancel the body without opening or retaining it; and
- stop before explaining the difference, merging versions, selecting a controlling file, or applying either response to a property or owner.
A newer filename does not prove that the body is more complete. A matching content length does not prove identical bytes. A changed MIME label does not explain the source content. A missing link does not prove that a file is invalid or legally superseded.
Prepare a neutral handoff when more work is authorized
A neutral handoff may contain the source-index ID, publisher-page URL, displayed section, four exact labels, four exact endpoints, endpoint families, retrieval timestamp, header-only observations, source limitation, one document-control state, and one unresolved question.
A safe unresolved question is: What authorized purpose, source version, minimum necessary data, privacy control, and qualified review are required before any file body or owner-specific interpretation enters scope?
Before record content is accessed, an authorized person should verify role, purpose, lawful basis, minimum-necessary scope, approved system, data handling, retention, recipient, and whether qualified appraisal, legal, or tax review is required. Keep the reusable public index free of record content and conclusions.
Final verification checklist
Before closing the source index, confirm that:
- the current official Culberson CAD Data and Records page was checked;
- all four displayed labels and exact endpoints were preserved separately;
- endpoint families were recorded without implying content structure;
- response bodies were cancelled and not retained, opened, previewed, parsed, sampled, searched, hashed, compared, normalized, or summarized;
- HTTP status, content type, and content length remain header observations only;
- no equivalence, completeness, accuracy, currentness, legal-certification, applicability, appraisal, tax, protest, legal, valuation, offer, or sale conclusion was made;
- no name, account, address, identifier, header, row, field, cell, legal description, property fact, value, classification, or personal data was exposed;
- the adjacent mineral-ZIP container record retains its separate complete-file and central-directory job;
- any later source difference remains
source-conflictwithout merging; - any file-body or record-content need forces
controlled-record-stop; - any individualized comparison, professional judgment, or action forces
authorized-human-stop; and - no credential use, property search, contact, upload, submission, payment, representation, negotiation, or promised result occurred.
The completed artifact should remain deliberately narrow: a source index for four current publisher-link relationships and their safe response-header boundary. It is useful because it shows where four differently delivered responses begin while refusing to pretend that link labels and HTTP headers can answer what the files contain or what an owner should do.
Frequently asked questions
Which four 2026 certified-roll links does Culberson CAD currently display?
The recorded Data and Records page displayed Real and Personal Geo PDF, Real and Personal Alpha PDF, Real and Personal Excel, and Certified Mineral Appraisal Roll ZIP links. Preserve each displayed label and exact endpoint separately.
Does this source index download or open the four files?
No. It records the publisher-page relationship and safely observable response headers, then cancels the response body. It does not download, retain, open, preview, extract, sample, search, parse, compare, normalize, or summarize file content.
Does HTTP 200 prove that a certified-roll file is correct?
No. HTTP 200 says that an endpoint responded successfully at the recorded time. A content type and content length describe that response. None proves file-body validity, completeness, accuracy, currency, legal certification, applicability, or a correct property result.
Are the PDF, Excel, and ZIP responses equivalent versions of the same records?
This public index makes no equivalence claim. Different endpoint families, MIME types, and lengths do not establish matching fields, rows, calculations, classifications, completeness, or legal status. Answering that question would require file-body access and an authorized review outside this article.
Where does the mineral ZIP container analysis belong?
The adjacent Culberson CAD Certified Mineral Roll ZIP Source-Control Record owns the recorded archive container, complete-file identity, and generic central-directory metadata. This four-format index ends at the publisher link and response-header boundary.
Sources reviewed for this article
- Culberson CAD, Data and Records (accessed 2026-08-27)
- Culberson County Appraisal District, official site (accessed 2026-08-27)
- Texas Comptroller, Culberson County Directory (accessed 2026-08-27)
- Texas Legislature, Tax Code Chapter 25 (accessed 2026-08-27)
- Texas Legislature, Tax Code Chapter 26 (accessed 2026-08-27)
A practical next step
Put your mineral rights in context.
Every mineral interest, royalty history, and written offer is different. Start with a question, or share what you have for a free underwriter review.
- Free
- Confidential
- No obligation to sell
Ready for a closer look?
Review the Mineral ZIP BoundaryGet a directional range with the assumptions clearly stated.