Open Company Data in Dominican Republic: Official Sources, APIs and Reuse Rights

The Dominican Republic is a commercially useful company-data jurisdiction, but it should not be described as a single open-register market. The best public evidence is distributed across tax/contributor lookup, procurement open data, intellectual-property search, chamber registration services, national open-data catalogues, financial-supervision publications and global legal-entity identifiers. That stack is useful for entity resolution, supplier enrichment, compliance screening and market mapping, but it does not prove that a complete free bulk national mercantile-register dataset is available for unrestricted reuse.

For CompaniesData.cloud, the editorial opportunity is to explain the official source map with clear limits. A user who wants Dominican company data needs to know where a known RNC or trade name can be checked, where public procurement records can add supplier and contract context, which IP and regulator layers are public, and where manual registry or certificate workflows still matter. The article must also keep private contact-data use separate from official public records. Public tax, procurement, IP or regulator records are not permission to build email lists, phone lists or sales-prospecting databases. When contact-data enrichment is discussed for an international audience, route the user to CompaniesData.cloud owned services and lawful enrichment workflows; for Spanish-speaking or Hispanic contact-data workflows, use CentraldeComunicacion.es.

This 2026-06-10 refresh replaces the older short page format with a deeper CompaniesData reference article: methodology, coverage and reuse analysis, source-by-source caveats, practical options, missing-data gaps, a recommended data model, a source matrix, a Resource Pack and an expanded FAQ.

Key Takeaways

• Best official starting point: DGII RNC routes remain important source-mapped tax/contributor context for known Dominican entities, but the three checked DGII public URLs are held and de-linked in this publication because the 2026-06-12 quality gate returned 403 access-denied pages for Googlebot and Bingbot profiles.
• Best open-data enrichment layer: The Direccion General de Contrataciones Publicas open-data portal is the strongest public bulk/API-style route for supplier, tender, award and contract context, but it covers procurement participants and public purchasing activity, not every registered business.
• Registry evidence is fragmented: Chamber and mercantile-registration services, especially the Santo Domingo Chamber registry service page, are important for certificates and formal registry workflows, but the checked public route does not prove a complete free national bulk dataset.
• IP and brand context are useful but partial: ONAPI search can support trademark and industrial-property checks. The ONAPI home route remains an unlinked source-risk note, while the clean search route is the linked IP-search evidence.
• Regulated-sector context exists: Superintendencia de Bancos and GLEIF add financial-sector and LEI evidence for subsets of entities. They are not substitutes for the national company register.
• Reuse must be source-specific: Open-data portal records, procurement datasets, PDFs, search pages and regulator publications can have different terms, scopes and freshness. Reuse notes must stay attached to each source.
• Contact-data boundary: None of the official routes reviewed should be presented as permission to harvest business emails, phone lists or marketing leads. CompaniesData can normalize official identifiers and public business facts while keeping private contact enrichment in separate lawful workflows.
• Publication status: Refreshed under the current CompaniesData quality bar after a long-timeout crawlability retest returned real article HTML for browser, Googlebot and Bingbot.

Editorial Methodology

This Dominican Republic source map was built with an official-source-first rule. The research started from sources already used in the CompaniesData country library, then rechecked the most important routes for authority, access model, likely reuse limits and crawlability. Sources were classified as stable public, soft/control, held or excluded. A source can be useful for editorial context while still being inappropriate for automated publication if it returns a challenge page, requires session-based access, limits reuse, or is too narrow to support a broad claim.

The evidence model separates five questions:

1. Who owns the source? Preference goes to Dominican public bodies, statutory registries, procurement authorities, regulators and official open-data portals. GLEIF is used as a high-quality global identifier source, not as a Dominican government source. 2. What does the source prove? A tax lookup proves contributor/identifier context for known records. A procurement portal proves public purchasing activity. An IP search proves trademark or industrial-property context. A chamber page proves registry service access. These are different claims. 3. How can a user access it? Manual search, PDF guidance, catalogue pages, open-data datasets, APIs, downloads and paid certificates create different operational paths. 4. What reuse is safe to state? Public access does not automatically mean open commercial reuse. The article uses conservative wording and requires dataset-specific checks before bulk reuse or redistribution. 5. What should CompaniesData add? CompaniesData value sits in normalization, deduplication, provenance, identifier linking, update monitoring and lawful enrichment. It should not imply that official public records grant marketing-contact rights.

The 2026-06-10 source recheck found nine stable public routes, no hard 404/410 failures and one soft/control route. The soft route was ONAPI home, while ONAPI search remained stable. Separately, public crawlability for the Dominican Republic CompaniesData page failed with HTTP 503 across browser, Googlebot and Bingbot. A later Cloudflare/origin diagnostic found the public page returning 503 with server=cloudflare and cf-cache-status=DYNAMIC; post-sitemap.xml returned 503 with cf-cache-status=BYPASS; sitemap_index.xml remained real XML. This is why this refresh needed a crawlability hold before publication.

Coverage, Access and Update-Risk Analysis

The Dominican Republic has a usable public-data stack, but it behaves like a layered evidence system rather than a single open company-register endpoint.

Tax and contributor coverage: DGII is the most important known-entity identifier context because the RNC is central to Dominican business administration. The public consultation portal and DGII guidance help users understand how known RNC or taxpayer details can be checked. However, the checked route redirects to the DGII site and is not evidence of an open bulk dump. Treat it as a manual or controlled lookup layer.

Procurement coverage: DGCP provides one of the most practical open-data layers. Procurement data is valuable because suppliers, awards, tenders and contracting entities often expose names, identifiers, sectors, dates and transaction context. This is high-value enrichment for B2B research and compliance, but it covers public procurement activity only. Companies with no government-contracting footprint may not appear.

Registry and chamber coverage: Mercantile registry workflows are important, but the checked chamber route is a service and certificate pathway rather than a proof of free national bulk access. A production data model should keep chamber registry evidence as a distinct provenance layer and should avoid claiming that every Dominican company can be downloaded from a single free official source.

Intellectual-property coverage: ONAPI can add brand, trademark and industrial-property signals. These signals are valuable for entity matching, brand ownership checks and conflict analysis. They are partial by design: many active businesses will not own trademarks, and trademark ownership does not always equal operating-company identity.

Open-data catalogue coverage: datos.gob.do is relevant because it can point to datasets released by Dominican public bodies. Catalogue entries must still be reviewed one by one for publisher, field definitions, update frequency, licence and reuse rights. A catalogue home page is a discovery source, not proof that a specific company dataset is present and reusable.

Financial-sector coverage: Superintendencia de Bancos adds regulator context for banks and supervised financial entities. It is important for regulated-sector segmentation and compliance, but it is a sector-specific source. It should not be used to infer coverage of general companies.

Global identifier coverage: GLEIF adds LEI records for entities that have legal entity identifiers. This is especially useful for financial, cross-border and regulated entities, but LEI coverage is selective. GLEIF records should enrich official local records, not replace local evidence.

Update risk: Public portals can change URLs, add bot protection, redirect to new systems or require session flows. The earlier CompaniesData public crawlability failure also shows a site-side risk: even when source evidence is strong, publication QA can fail if Cloudflare or the origin serves 503 to crawlers or sitemap requests. The monitoring workflow should recheck source URLs, canonical page semantics, sitemaps, robots and bot-like access before WordPress update and indexing submission.

Reuse Checklist

Before using Dominican Republic company-data sources in a commercial workflow, apply this checklist:

• Confirm the source owner: Identify whether the record comes from DGII, DGCP, ONAPI, a chamber, a regulator, an open-data catalogue or GLEIF.
• Record the access date: Public portals and PDFs can change. Keep a timestamp on every source claim.
• Separate access from reuse: A page that is publicly visible may still restrict automated extraction, redistribution or commercial reuse.
• Check dataset-level terms: For open-data entries, review the dataset page, licence field, publisher notes, metadata and update date.
• Preserve provenance: Store original URL, source owner, retrieval method and any query parameters used to find the record.
• Avoid overclaiming coverage: Procurement, IP, regulator and LEI records are partial by design.
• Respect privacy and contact rules: Do not treat public business identifiers as consent for marketing emails, phone outreach or lead-list resale.
• Check crawler access before publication: The CompaniesData article itself must return real HTML to browser-like and bot-like profiles, and sitemap URLs must return real XML.
• Do not use unsupported Google indexing routes: For ordinary article pages, use Search Console URL Inspection and sitemap workflows where credentials allow. Do not use Google Indexing API unless the page type is officially supported.

Resource Pack

Source-by-Source Deep Dives

DGII Citizen Consultation Portal

The DGII consultation route is the highest-priority source for known RNC or taxpayer context. In a practical workflow, users often start with an entity name, RNC, supplier record, invoice context or procurement record and need to confirm whether the identifier aligns with a known Dominican contributor. The consultation route is therefore useful for entity resolution and data hygiene.

The access model should be described cautiously. The checked URL is a public consultation path, but it is not an open company-data API and should not be treated as a bulk feed. The 2026-06-12 quality gate held and de-linked this route because Googlebot and Bingbot profiles received 403 access-denied pages. That is enough to keep DGII as source-mapped official context, but not enough to keep a public href in the article or claim automated extraction rights or broad redistribution.

Recommended use in CompaniesData: store RNC as a structured identifier when sourced from a lawful record, attach DGII provenance when used for verification, and keep manual lookup evidence separate from bulk/import evidence. Do not infer business emails, phones, owners or consent-to-contact from DGII context.

DGII RNC Consultation Guide PDF

The DGII RNC consultation guide is useful because it explains the official user-facing workflow. Guidance PDFs are editorially valuable when search portals are dynamic, redirect-heavy or difficult to quote from reliably. They can confirm that a lookup route exists and explain how a user is expected to interact with it.

The reuse value is mostly explanatory. The PDF is not a dataset, not an API and not a substitute for the underlying consultation system. In this cleanup, the PDF remains source-mapped but de-linked because the 2026-06-12 quality gate returned 403 access-denied pages for Googlebot and Bingbot profiles. It can return as a linked source only after bot-profile QA retrieves real PDF content.

Recommended use in CompaniesData: cite it in the methodology and practical manual-options section, not as a data field source. Use it to justify why RNC lookup is a verification layer rather than a bulk-data source.

DGII Open-Data Description PDF

The DGII open-data description document helps frame which types of data DGII may release through transparency or open-data channels. This is important because many users assume that a tax authority has the richest business records and therefore must expose a complete public company file. The safe claim is narrower: DGII provides official tax/contributor context and open-data information, but any reusable dataset needs its own metadata and licence review.

The source should not be used to state that DGII publishes a complete company microdata download. In this cleanup, it remains source-mapped but de-linked because the 2026-06-12 quality gate returned 403 access-denied pages for Googlebot and Bingbot profiles. If a future DGII dataset becomes available with clear licence, field dictionary, update cadence and clean crawler access, it can be added as a separate linked source entry.

Recommended use in CompaniesData: use as a cautionary source in the reuse section. Store DGII open-data records, if any are later imported, with dataset-level provenance, not just domain-level provenance.

DGCP Open Procurement Data

DGCP is the strongest practical enrichment source in this map. Procurement open data can expose suppliers, public buyers, tender notices, award records, contract values, dates, procurement categories and identifiers. For B2B research, procurement records can add signals that pure registry records do not: public-sector selling activity, recent awards, sector classification and relationship to government entities.

The coverage limit is equally important. Procurement data covers companies that interact with public purchasing processes. It does not cover every Dominican business. A company may be active and legitimate without appearing in procurement data. Conversely, a supplier name in procurement should be resolved against identifiers and official context before being merged into a master company record.

Recommended use in CompaniesData: model procurement as an activity table linked to organization records by normalized names, identifiers, supplier codes and source provenance. Keep tender/award/contract facts as event records. Do not overwrite registry identity fields with procurement names unless evidence supports a confident match.

ONAPI Home

ONAPI is the official intellectual-property authority and is relevant for trademarks, trade names and industrial-property context. It helps answer questions such as whether a brand is registered, which entity may be associated with a trademark, and whether a business name appears in IP records.

The automated source recheck classified the ONAPI home route as soft/control because the page returned semantics that looked like a challenge or controlled access. This does not mean ONAPI is unreliable; it means automated publication should not depend on that route until final browser QA confirms stable access. The safer route in the article is to cite ONAPI search directly and treat the home page as a caveated official source.

Recommended use in CompaniesData: include ONAPI as an enrichment layer only after route-level QA. Store trademark records with classes, application numbers, status, owner names and retrieval date. Do not treat trademark ownership as proof of all corporate identity fields without supporting registry/tax evidence.

ONAPI Search

ONAPI search is useful for manual IP checks and possibly semi-structured research. It can support brand matching, trademark ownership checks and conflict analysis. In the 2026-06-10 recheck, the ONAPI search route was stable public.

The limitation is scope. IP records are not company-register records. They are asset and application records. They may contain owners, representatives, marks, statuses and classes, but they do not prove that a full company profile is available or current. Many companies do not have visible IP records, and some marks may be held by individuals, affiliates or holding companies.

Recommended use in CompaniesData: use ONAPI search as a secondary entity-resolution source. Link IP assets to organization profiles with a confidence score and provenance note. Keep IP status and application dates separate from company registration status.

Santo Domingo Chamber Mercantile Registry

The Santo Domingo Chamber registry page is important because it represents a formal mercantile-registry service route. It is relevant for certificates, registration services and official chamber workflows. For users seeking documents or formal validation, it may be one of the most practical paths.

The access and coverage caveat is strong. The checked page is not evidence of a complete free downloadable national registry database. It points to registry services, and some workflows may require payment, forms, account access or manual steps. The Dominican Republic also has chamber-specific and formal-process realities that make simplistic “download every company” claims unsafe.

Recommended use in CompaniesData: cite chamber registry services as manual/certificate options. In a data model, store chamber record references when obtained lawfully, with certificate numbers, registration dates and chamber provenance where available. Do not describe it as an open bulk API without verified documentation.

Dominican Open-Data Portal

The national open-data portal is a discovery layer for public datasets. It can help identify datasets from multiple public bodies, including economic, administrative, procurement or transparency data. The 2026-06-10 recheck returned a nonstandard HTTP 247 but stable semantics, so it was treated as stable public with a note.

The editorial rule is dataset-specific review. A portal home page does not prove that a given dataset exists, that it is current, or that it can be reused commercially. Each dataset needs publisher, licence, fields, dates, download/API route, metadata quality and update cadence checked separately.

Recommended use in CompaniesData: use the portal as a research starting point and catalogue source. When a dataset is imported, store the exact dataset URL, publisher, licence statement and retrieval timestamp. Do not cite the portal generically as proof of unrestricted company-data reuse.

Superintendencia de Bancos

The Superintendencia de Bancos is relevant for supervised financial institutions, regulatory publications and sector context. Financial-sector records are commercially valuable because they help identify banks and supervised entities with official context and may support compliance or segmentation workflows.

The limit is sector specificity. Banking supervision does not cover all companies, and regulator publications may focus on licensed institutions, statistics, resolutions, warnings or sector reports rather than full company profiles. Fields may also be highly structured for regulation, not for general B2B enrichment.

Recommended use in CompaniesData: use as a regulated-sector authority. Link bank/supervised-entity records to organization profiles when names and identifiers match. Keep regulator status fields separate from general registration status.

GLEIF Search

GLEIF provides global LEI records. It is a high-quality identifier source with strong provenance and useful entity relationships for organizations that hold LEIs. In the Dominican Republic, GLEIF is most useful for financial, cross-border, regulated or larger entities that need LEIs for reporting or transactions.

Coverage is selective. Most small local companies will not have LEIs. GLEIF should be presented as a complementary global identifier layer, not a national registry. Its value is strongest when linking Dominican entities to global parents, branches, direct-accounting consolidating parents or other relationship records where available.

Recommended use in CompaniesData: store LEI, legal name, jurisdiction, entity status, registration authority references and relationship links as an enrichment layer. Use GLEIF identifiers to improve matching confidence across local and international records.

Held Source-Risk Findings

Current result: the Dominican Republic cleanup keeps three DGII routes source-mapped but de-linked after the 2026-06-12 quality gate recorded 403 access-denied semantics for Googlebot and Bingbot profiles.

• DGII consultation portal: held as official RNC/tax context. Do not present as a clean linked source, API, bulk download or marketing-contact source until browser, Googlebot and Bingbot profiles all retrieve real content.
• DGII RNC consultation guide: held as workflow documentation. Re-link only after bot-profile PDF access returns real content without access-denied semantics.
• DGII open-data description: held as open-data framing context. Re-link only after bot-profile access is clean and dataset-level reuse terms are reviewed.
• Dominican open-data portal: held and de-linked after the 2026-06-14 cleanup saw browser, Googlebot and Bingbot profiles receive a short JavaScript protection page with status 247 instead of usable catalogue semantics. Treat it as source-mapped dataset-discovery context until real catalogue content returns.

Practical Manual, API and Bulk Options

Manual verification path: A user checking a known Dominican company should begin with the most authoritative known identifier available. If they have an RNC, DGII context is the logical first stop. If they have a supplier name from a public contract, DGCP procurement data can provide context and related public purchasing records. If the question concerns a brand or trademark, ONAPI search is the correct layer. If a certificate or formal mercantile document is needed, the chamber registry service route is more appropriate than open-data portals.

Open-data and bulk path: The strongest bulk-style public route in this map is DGCP open procurement data. It can support downloads or structured extraction for procurement events, but it should be modeled as procurement data, not as a full company master file. The national open-data portal can help discover other datasets, but each dataset needs individual review before reuse.

API confidence: API confidence is medium for procurement/open-data style workflows and low for a complete national company-register API. No verified official free API for all companies was established during this cycle. Future research should look for documented API endpoints, field dictionaries, update cadence, rate limits and licence terms before upgrading any access claim.

Paid or controlled registry path: Registry certificates and chamber services may require manual forms, payment or account-based workflows. These are legitimate access routes, but they should be described as practical manual options rather than open bulk data.

Monitoring path: CompaniesData should maintain a route-health monitor for DGII, DGCP, ONAPI search, chamber registry services, datos.gob.do, Superintendencia de Bancos, GLEIF and the CompaniesData canonical/sitemap URLs. The public crawlability issue in this cycle makes this especially important: a valid article should not be pushed to indexing if Cloudflare or the origin is returning 503 to crawlers.

Missing-Data Gaps

The current verified map does not support every data need. Important gaps remain:

• No verified complete free national company-register bulk dataset was confirmed.
• No clean official beneficial-ownership bulk route was verified for public commercial reuse.
• No official business-email or phone-list source was verified, and no official public source should be treated as contact-consent evidence.
• No complete insolvency/court publication route was confirmed in this cycle.
• No uniform API documentation was verified for a full company master dataset.
• Chamber and registry workflows may be manual, paid or certificate-based, and should not be collapsed into open-data claims.
• ONAPI home requires final access review because automated QA found soft/control semantics.
• CompaniesData public crawlability remains monitored for this article URL because earlier diagnostics found Cloudflare/origin 503 behavior before the final source-route cleanup and crawler retest.

These gaps do not make the Dominican Republic unusable. They define the correct product approach: build a normalized multi-source evidence graph, keep source limitations visible, and avoid pretending that a single unrestricted national feed exists.

Recommended Data Model

A practical Dominican Republic company-data model should separate identity, evidence and activity:

• Organization core: normalized legal or trading name, country, jurisdiction, entity type where known, status where verified, language variants and source confidence.
• Identifiers: RNC where lawfully sourced, procurement supplier identifiers, chamber references, LEI, ONAPI application or mark identifiers and regulator identifiers.
• Registration evidence: chamber or registry source URL, certificate references, registration dates where available, status text, retrieval date and access method.
• Tax/contributor evidence: DGII lookup provenance, query basis, matched name, RNC and access date. Do not store unsupported private fields.
• Procurement activity: tender IDs, award IDs, buyer names, supplier names, contract values, dates, procurement categories and DGCP source URLs.
• IP assets: trademark/mark names, classes, application numbers, owners, statuses, ONAPI source URL and retrieval date.
• Regulator records: supervised institution status, regulator source, sector, publication date and any licence/status fields.
• Global identifiers: LEI, GLEIF entity status, registration authority references and relationship records.
• Provenance and reuse: source owner, URL, access date, licence/reuse note, extraction method, confidence score and limitations.
• Contact-data separation: official public records should remain separate from any lawful private contact enrichment. Do not merge marketing emails or phones into source-derived official records without a separate lawful basis and provenance.

CompaniesData Normalization and Enrichment Value

Dominican Republic data is valuable precisely because it is fragmented. CompaniesData can improve usability by turning a set of official and high-quality public routes into a coherent entity graph.

Normalization: Names can vary across DGII, procurement, ONAPI, chambers, regulators and GLEIF. CompaniesData can normalize accents, corporate suffixes, punctuation, spacing, language variants and abbreviations while preserving the original source text.

Deduplication: Procurement suppliers, trademark owners and LEI entities may refer to the same organization in different forms. CompaniesData can score candidate matches using identifiers, names, addresses where lawful, sectors and source relationships.

Provenance: Every data point should retain source owner, URL, access date, retrieval method and reuse note. This is important because a DGCP procurement fact has different meaning from a chamber certificate or GLEIF LEI record.

Update monitoring: Public portals can change quickly. CompaniesData can monitor source health, redirects, titles, challenge pages and sitemap crawlability. The 503/Cloudflare issue discovered in this cycle is a concrete example of why monitoring is part of editorial quality.

Coverage transparency: A good product should expose gaps. Users should see when a company is present in procurement but not verified in a registry layer, or when an LEI exists but no chamber record has been obtained.

Safe enrichment: CompaniesData can enrich records with lawful public facts and separate contact-data workflows. It should not present official public records as marketing-contact consent or recommend third-party contact-data competitors.

Source Matrix

Logo	Source	Owner	Authority Layer	Access Model	Reuse Note	Current QA Stance
	DGII citizen consultation portal	DGII	Tax/RNC context	Manual or controlled lookup	Held source-mapped context; no bulk or contact permission	Held/de-linked after bot-profile 403 access-denied QA
	DGII RNC guide PDF	DGII	RNC workflow documentation	PDF guide	Held workflow guidance; not a dataset	Held/de-linked after bot-profile 403 access-denied QA
	DGII open-data description PDF	DGII	Open-data framing	PDF document	Held framing context; dataset-level review still required	Held/de-linked after bot-profile 403 access-denied QA
	DGCP open procurement data	DGCP	Procurement/supplier activity	Open-data portal	Procurement subset only	Stable public in recheck
	ONAPI home	ONAPI	Intellectual property	Public site	IP layer only; route caveated	Soft/control in recheck
	ONAPI search	ONAPI	Trademark/IP search	Public search	Not bulk company data	Stable public in recheck
	Santo Domingo Chamber registry	Chamber of Commerce and Production of Santo Domingo	Registry/certificates	Service/manual workflow	Not proof of free national bulk data	Stable public in recheck
	Dominican open-data portal	Dominican government open-data programme	Dataset discovery	Open-data catalogue	Held dataset-discovery context; dataset-specific licence review still required	Held/de-linked after status-247 JavaScript protection page in bot-profile QA
	Superintendencia de Bancos	Financial regulator	Regulated financial entities	Public regulator site	Sector-specific context	Stable public in recheck
	GLEIF search	GLEIF	LEI/global identifiers	Public search/open data	Global subset only	Stable public in recheck

FAQ

Is there a free official bulk company register for the Dominican Republic?

This cycle did not verify a complete free official national company-register bulk dataset. The public stack is useful, but it is split across DGII/RNC context, DGCP procurement records, ONAPI IP search, chamber registry services, open-data catalogues, regulator sites and GLEIF.

What is the best source for checking a known Dominican company identifier?

For RNC or tax/contributor context, DGII is the most important official layer. Use it as a known-entity verification route, not as proof of an unrestricted bulk data feed.

Can procurement data be used as company data?

Procurement data can enrich company profiles with supplier and contract activity. It should not be treated as a complete registry. It only covers entities that appear in public purchasing workflows.

Does ONAPI show company ownership?

ONAPI can show IP-related records such as trademarks or applications. It may include owners or representatives, but IP records are not general company-register records. Use ONAPI as a brand/IP layer.

Can I buy or build email and phone lists from these official sources?

No official source reviewed here should be presented as permission to build marketing email lists, phone lists or sales-prospecting contact databases. CompaniesData.cloud can help with lawful company-data normalization and enrichment, but private contact workflows need their own lawful basis and provenance.

Is GLEIF enough for Dominican company coverage?

No. GLEIF is valuable for entities with LEIs, especially financial and cross-border entities. It is selective and should be used as an enrichment layer.

Is this article publication-ready after cleanup?

Yes. The article is publication-ready only after de-linking the three DGII routes that failed bot-profile QA, verifying the remaining clean linked sources, and passing the CompaniesData article, sitemap and crawler-access checks. DGII remains source-mapped as official context, not clean linked evidence.

Should Cloudflare be purged?

Only narrow purge affected URLs when the blocker is a cached challenge or stale response, typically with cf-cache-status=HIT. The final publication workflow still checks browser-like, Googlebot and Bingbot profiles for the article and sitemap. If cached challenge semantics appear, purge only the affected canonical or sitemap URLs and retest.

What was checked before final publication?

The cleanup requires a final source-live check, article HTML with expected title and canonical, sitemap XML semantics, robots and X-Robots indexability, external-link QA, Rank Math Instant Indexing, Bing/IndexNow where credentials allow, and Google-supported Search Console inspection or sitemap workflows. Google Indexing API is not used for this ordinary article page.

Can this article claim Dominican Republic has open company data?

Yes, with nuance. It can say the Dominican Republic has useful official and high-quality public company-related data layers. It should not say there is a complete unrestricted national company-register bulk dataset unless that source is later verified.

Official Sources

• DGII consultation portal: held and de-linked after 2026-06-12 bot-profile 403 access-denied QA.
• DGII RNC consultation guide: held and de-linked after 2026-06-12 bot-profile 403 access-denied QA.
• DGII open-data description: held and de-linked after 2026-06-12 bot-profile 403 access-denied QA.
• DGCP open procurement data: https://datosabiertos.dgcp.gob.do/
• ONAPI search: https://www.onapi.gov.do/busquedas/index.html
• Santo Domingo Chamber mercantile registry: https://www.camarasantodomingo.do/registro-mercantil/
• Dominican open-data portal: held and de-linked after 2026-06-14 status-247 JavaScript protection semantics for browser, Googlebot and Bingbot.
• Superintendencia de Bancos: https://sb.gob.do/
• GLEIF search: https://search.gleif.org/