Measured evidence for supplier decisions, free to cite with its dates.
Choose a study for the decision in front of you: matching a company name, reading its records or checking a factory claim. Each finding includes its sample, date and limits. For field-by-field explanations, read the China-side field notes.
Nineteen studies measure something a buyer may need to decide. The last covers our interface translation review. Each states its sample, date and limits.
Registry versus database. 17 records compared (registry observations dated 5 September 2026; database baseline 28 August). Presence and text-length checks do not establish full record equality.
China company registry availability (measured 5 and 8 August 2026). The request profiles differed; controls, later observations and a withdrawn claim are explained in the study.
The measurements this site’s claims rest on. Each states its frame and measurement date. Some enumerate a fixed list; others use selected profiles or query inputs. Their rates do not estimate all Chinese suppliers.
Measurement
What it establishes
Frame
Taken
Registered-scope census
Import-export wording appeared in 197 of 264 records (74.6%)
264 companies, whole frame
8 Aug 2026
Change-log census
How fast the official record moves: 54.9% amended within 12 months, median 39 changes
Same 264 companies
8 Aug 2026
Official-source availability
Five of eight hosts returned no HTTP 200; browser searches were not tested
8 targets: 1 CLI + 3 browser-UA requests each; 2 controls: 1 of each
8 Aug 2026
Check-character strength
USCI catches 100% of single-character errors; VIN catches 92.5%
2.9 million injected errors, fixed seed
9 Aug 2026
Single-result confirmation
What a name search returns: 42.5% nothing, 50.9% exactly one row
106 names from the selected vPIC frame
August 2026; date discrepancy in study
Report-menu source mapping
153 menu items each named a source; this did not test successful retrieval or delivery
153-item saved menu
22 Aug 2026
Correction, 10 September 2026: we withdrew the earlier claim that 134 of the 153 report checks are read automatically, because we cannot show it. What holds: each of the 153 checks names its data source, which does not mean data comes back for every company. The linked studies give each finding’s frame and method; a complete count of a chosen list does not make it representative.
Media kit: graphics, captions and reuse terms
For editors and researchersPublication-ready assets
Research media kit
Three findings are packaged below as 1200 × 675 graphics, with datasets, DOIs and corrected captions. The graphics and captions retain the sample, date and limits with each finding.
1. English-name fields matched for 47 of 106 inputs
47 of 106 inputs had a top result with a matching English-name field. Measured 12 August 2026.
Frame: 106 China-listed trailer manufacturers in NHTSA vPIC, searched using the name held in that register. Taken: 12 August 2026; two same-platform runs seven hours apart reportedly returned the same counts.
Limit: Name-field equality does not confirm identity. This dated trailer group is not a population estimate or an upper bound for other suppliers. Interpretation and graphic labels corrected 8 September 2026.
Copy-ready caption:
Currawong recorded matching English-name fields for 47 of 106 inputs (44.3%) from a China-listed trailer manufacturer frame. The fields came from the top results on one business-information platform. Name equality does not confirm identity or predict results for other suppliers. Measured 12 August 2026.
2. Import-export wording appeared in 197 of 264 records
Frame labels corrected 8 September 2026. The SVG and PNG now state that the original provincial-list attribution remains unverified. Counts and the 8 August query date are unchanged.
197 of 264 registrations carried import-export wording. Queried 8 August 2026.
Frame: 264 names in the saved study frame: Shandong 136, Anhui 113 and Yunnan 15. The original notes attribute these to provincial ‘Little Giant’ lists; full verification against the originals remains open. These counts describe the saved frame, not all Chinese suppliers. Queried: 8 August 2026.
Limit: Scope wording does not prove current export capacity, required licences, product capability, or shipment history. Absence of the wording is a follow-up signal. It is not a verdict.
Copy-ready caption:
Currawong found import-export wording in 197 of 264 registrations (74.6%) in its saved 264-name frame. The original provincial-list attribution remains unverified. Registered scope wording is not proof of current export capacity. Queried 8 August 2026.
Frame labels corrected 8 September 2026. The SVG and PNG now state that the original provincial-list attribution remains unverified. Counts and the 8 August query date are unchanged.
145 of 264 registrations changed within 12 months. Queried 8 August 2026.
Frame: the same saved 264-name frame, using returned change dates and category labels. Its original provincial-list attribution remains unverified. Queried: 8 August 2026. Within the frame, 207 of 264 changed within 24 months and the median lifetime change count was 39.
Limit: A registered change is not itself a risk finding. The field that changed, its before-and-after facts and its relevance to the transaction determine whether it matters.
Copy-ready caption:
Currawong found that 145 of 264 registrations (54.9%) in the saved 264-name frame changed within the prior 12 months. The original provincial-list attribution remains unverified. A registered change is not itself a risk finding; the changed field and transaction context matter. Queried 8 August 2026.
What this desk has actually measured, counted on 22 August 2026
The studies below are the written-up ones. Underneath them sits a larger body of measurement that reaches the guides without ever becoming a study of its own. A fill-rate table sits on one page, a probe result on another. This is a count of the whole thing, taken mechanically from the pages themselves.
Original measurement carried by the English pages. Counted 22 August 2026.
Measurement
Pages carrying it
Registry field fill rates (45 selected company codes × 19 dimensions)
40
Official-source availability from two vantage points
“Little Giant” scope-wording census (264 companies)
21
Registry population counts by name ending
7
Historical delivery-tier markers; timings not established
6
Company-name uniqueness across three spellings
6
USCI check-digit error detection
5
Six further measurement sets
8
Thirteen distinct measurement sets, carried by 99 English pages, with query dates spanning 8–22 August 2026. Every table on this site states which set it came from and the date it was queried. A measurement without a date stops being evidence at some point, and nobody can tell when.
Two honest notes on this count. It is a mechanical inventory. We counted the evidence markers embedded in the pages, not the quality of what they show. And several sets are read along different dimensions on different pages: the 45-code lookup frame alone appears on 40 pages, which is one sample answering forty questions, not forty studies.
That distinction matters enough that every page carrying it says so in its own footnote. If you are citing any figure from this site, cite the underlying set and its query date rather than the page you found it on. Method for the largest set: the NHTSA manufacturer census.
Alibaba and 1688: subject-identity fields
Original study92 compared · 94 records
Alibaba vs 1688: Chinese-name fields 0/33 vs 59/59
If a profile does not give you a clear registered identity, ask for the business licence before payment. We compared the fields found in 92 profiles. The source records contain useful clues, but they do not confirm the seller.
Measured 28 August 2026 · Comparison: 59 on 1688 + 33 on Alibaba.com; controls and probes explained below · Prepared by Bao L. Zhou, Currawong’s China-side verification desk.
Platform subject fields: key counts and badge coverage
Field a buyer needs
1688 (59 profiles)
Alibaba.com (33 profiles)
Registered Chinese name
59 of 59
0 of 33
Company principal field
59 of 59
0 of 33
Registered capital
57 of 59
0 of 33
Registration-code key found
59 of 59
0 of 33
: value passed both format checks
43 of 59
0
: value had 15 digits
8 of 59
—
: field key found; no string value extracted
8 of 59
—
The download holds 94 supplier profiles, with 92 profiles in the comparison across six product categories (59 on 1688 plus 33 on Alibaba.com: 30 category profiles and 3 earlier probes). Two 1688 entries are 2 control records, and 2 excluded shops had no retrievable factory card. On 1688, 43 of the 59 code strings passed both the GB 32100-2015 check-digit test and the six-digit administrative-division segment check. Eight held 15-digit legacy numbers, and eight had the key present with no extracted string. A missing string does not establish why a value is missing. One candidate passed the check digit by chance while failing the six-digit division check. On the 33 Alibaba.com profiles, the searched keys for Chinese name, company principal (companyPrincipal) and registration code were absent across all 33 records. That held across every assessor (SGS, TÜV Rheinland, or none) and badge tier (Verified supplier, Verified factory, or unbadged). You can validate any 18-character code offline or compare with our English-name lookup study (44.3% top-candidate match across 106 NHTSA vPIC names). Full walk-through: Alibaba.com vs 1688 supplier identity fields.
Method limits
Platform layouts change. A one-day snapshot shows only what the parser found on 28 August 2026.
Selection frame: The 1688 profiles were selected for a retrievable factory card. Suppliers without a card were not measured. The results do not set a bound for those suppliers.
Presence only: we checked whether fields were present, not whether the values are true, and this study does not evaluate the badges.
Verification challenges: both platforms triggered human challenges, so the run is not reproducible unattended.
Citing the platform subject-field study
Row-level records: CSV · JSON. (Reading correction noted 8 September 2026 on the standalone study page.)
Currawong, “Alibaba and 1688 identity fields: dated source-record comparison”. 92 compared profiles, drawn from 94 retained records across Alibaba.com and 1688, 28 August 2026. https://currawongweb.com/verify/alibaba-vs-1688-supplier-legal-name/ Dataset: https://doi.org/10.5281/zenodo.22136065
BibTeX
@dataset{currawong_platform_subject_fields_2026,
author = {Bao L. Zhou},
title = {{Subject-identity fields on Chinese supplier profiles: Alibaba.com and 1688 compared (94 profiles, August 2026)}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22136065},
url = {https://doi.org/10.5281/zenodo.22136065}
}
This study reports field presence, not a service claim. Currawong verifies public records on request and states sources, query dates and limits with every result; it does not certify suppliers.
NHTSA: record age and field completeness
Original study106 regulator records · 19 scored fields
Told to check the regulator’s record? Here is what is actually in it.
Use the named contacts as leads to check. We scored 19 fields in 106 vPIC records on 28 August 2026. Field presence does not prove that the details are correct or that a factory can make your product.
What the record holds, and how old it is
Selected fields in 106 vPIC records. Queried 28 August 2026.
What the record holds
Manufacturers
Share
Principal name and position fields present
106 of 106
100%
Carries a contact phone
104 of 106
98.1%
Carries a contact email
97 of 106
91.5%
Common-name field present
22 of 106
20.8%
Lists any equipment item
10 of 106
9.4%
Primary-product field present
0 of 106
0%
Selected fields in 106 vPIC records. Queried 28 August 2026.
Time since the stated LastUpdated date, measured on 28 August 2026.
Record last updated
Manufacturers
Share
Within the last year
28 of 106
26.4%
Over one year ago
78 of 106
73.6%
Over three years ago
37 of 106
34.9%
Over five years ago
21 of 106
19.8%
Over eight years ago
17 of 106
16.0%
Median record age is 2.1 years. The oldest original submission on the frame dates from 11 December 2004, the newest from 8 July 2026; three records have the same submission and last-update date. This does not show whether their contents changed that day.
Different sources answer different questions
Our separate 264-company registry study found 54.9% amended their registration within twelve months. Here, 73.6% of 106 vPIC records had a stated update date over a year old. These are different groups, fields and dates. The figures do not set a recheck interval or rank the two sources.
Keep the source and date beside each fact. A vPIC contact can help you ask for current details; it does not confirm the Chinese legal entity or the payee. Check those against your order documents. A record date alone does not tell you whether a fact is still correct.
One more thing the frame shows about record quality: the province field is not normalised. Shandong appears as both Shandong and SHANDONG, Henan as both Henan and HENAN. Anyone counting by province from this source without folding case will split one province into two.
Method, and what this study cannot say
The frame is the 106 China-listed trailer manufacturers in our vPIC census of 9 August 2026. On 28 August, we made one request per ID to the public manufacturer-detail endpoint, with no retry and a quarter-second gap. All 106 returned a record. This is the whole fixed frame, not a sample of all Chinese suppliers.
We scored 19 fields. A missing key was absent. A null value, blank string or empty list was empty; other values were present. All scored keys were returned. These states do not explain why a value is missing. The download retains the states and selected values. Full API responses are not retained. Dates come from LastUpdated and SubmittedOn.
All 106 records had a non-empty VehicleTypes list, while PrimaryProduct was empty. A declared vehicle type is a clue to check, not proof of production capability. The 22 non-empty Mfr_CommonName fields were not checked against legal names.
What it cannot say
A stale record is not evidence of anything wrong. Age measures time since the stated date. It does not explain why that date has not changed.
We did not verify a single value. Presence of an address or a principal is not proof that either is current or correct.
One regulator, one industry, one day. Trailer manufacturers in a US database. Other regulators keep different fields to different standards.
“Last updated” is the regulator’s own field. We report what it says; we cannot see what changed, or whether an update was substantive.
It says nothing about capability. That the record omits primary product is a fact about the record. It is not evidence that the company makes nothing, or anything in particular.
Citing the regulator-record study
Interpretation corrected 8 September 2026. This page now limits claims to the retained fields and dates. The original downloads are unchanged; no records were fetched again for this correction.
You may quote or reproduce these figures, including commercially, provided the measurement date, the frame and the stated limits travel with them. One row per manufacturer, with the three-state reading for all 19 scored fields and both dates, is in the result file (JSON).
Archived copies, each with its own DOI, resolving independently of this site: Zenodo · Harvard Dataverse.
A citation with everything it needs:
Currawong, “Told to check the regulator’s record? Here is what is actually in it”, 19 scored fields and record dates for 106 China-listed trailer manufacturers in NHTSA vPIC, 28 August 2026. https://currawongweb.com/research/#vpic-record-age Dataset: https://doi.org/10.5281/zenodo.22144964
BibTeX
@dataset{currawong_vpic_manufacturer_records_2026,
author = {Bao L. Zhou},
title = {{What a US vehicle regulator holds on 106 China-registered manufacturers, and when it was last updated}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22144964},
url = {https://doi.org/10.5281/zenodo.22144964}
}
This study reports what a public regulator record contains and when it was last updated. It is not an assessment of any manufacturer, and Currawong does not certify suppliers.
FDA: device enforcement records for firms in China
Original study264 enforcement records · 46 firm names
FDA: 264 records, 80 recall events, 46 Chinese firm names
A recall record should prompt a case-specific review, not an automatic supplier verdict. This study covers every device enforcement record the US regulator returned for a recalling firm located in China: 264 records. We counted what the public corrective-action trail shows.
Firm names and status labels in the saved records
How 264 enforcement records group by recalling-firm name. Queried 28 August 2026.
Where the records sit
Records
Share
Records with a firm name that appears more than once
241 of 264
91.3%
Records with the three most frequent firm names
139 of 264
52.7%
Records with the most frequent firm name
88 of 264
33.3%
Firm names appearing exactly once
23 of the 46
Status, seriousness and origin of the same 264 records. Queried 28 August 2026.
What the record says
Records
Share
Labelled Ongoing
219 of 264
83.0%
Labelled Ongoing; initiated over a year before the query
201 of 264
76.1%
Labelled Terminated
43 of 264
16.3%
Labelled Completed
2 of 264
0.8%
Class I: reasonable probability of serious harm
32 of 264
12.1%
Ordered by the regulator rather than firm-initiated
25 of 264
9.5%
Among records labelled Ongoing, the median time from initiation to 28 August 2026 was 875 days; the longest was 3,600. These are date differences, not measured times to closure. Initiations run from 8 June 2012 to 21 April 2026, with 43.2% of the whole frame initiated during 2024 alone.
Re-run on 7 September 2026 with the same query and the same de-duplication. Fourteen fixed measures matched. The two elapsed-time measures increased by ten days. This aggregate comparison does not prove that every underlying record was unchanged. The reproduction file is fda-china-device-enforcement-2026-09-07.json. A live read on 11 October 2026, with the same query and the same de-duplication, returned 267 records and 48 firm names. The 28 August counts above stay as published. Three more records appear (initiations now run to 31 July 2026), 222 carry the Ongoing label, and the largest firm name still has 88 records. The file is fda-china-device-enforcement-2026-10-11.json.
What to check before drawing a conclusion
A recall concerns a product problem and the action taken to address it. It does not settle the quality of a supplier or every product it sells. Nor does absence from this dataset show that a supplier is safe. Match the product and reason to your order, then check the current case information.
The 23 firm names appearing more than once account for 241 records (91.3%). But only 9 firm names have more than one event ID. The name with 88 records has one event ID. Record counts alone cannot establish repeated incidents.
We fetched all rows for country:"China" from openFDA’s device enforcement endpoint. The row count matched its reported total. No sampling or retry. Country means where the recalling firm is located, not where goods were made or sold. We parsed the YYYYMMDD dates and grouped firm names after trimming spaces and ignoring case.
What it cannot say
It is not a supplier ranking, and we publish none. The record file carries the firm names the regulator publishes; this page reports distributions only.
Absence proves nothing. Not appearing in this dated device-recall frame is not a clean bill of health.
Devices only. One regulator, medical devices only. Other sectors have different records and different reporting cultures.
Ongoing is a filing state, not a safety state. We report the saved label; it cannot establish the current case status or whether the issue was fixed.
Names are not verified entities. Two spellings can split one firm; a shared name can combine firms. We did not resolve these cases.
Citing the enforcement-record study
You may quote or reproduce these figures, including commercially, provided the measurement date, the frame and the stated limits travel with them. The CSV contains aggregate measures. The JSON contains one row per enforcement record, including its event ID, classification, stored status, dates and stated reason. Download the result file (JSON).
Corrected archive copies with unchanged counts, published 11 October 2026: Zenodo v2 · Harvard Dataverse v2.0. Earlier versions remain available. Use a corrected copy for new citations.
Interpretation corrected 8 September 2026. We withdraw the claims about time still open and repeated incidents. The saved JSON files and external archives keep their old labels. Read them with this correction. Raw data and the 28 August query date are unchanged. See the openFDA field reference.
A citation with everything it needs:
Currawong, “When it goes wrong in the US market, what does the record show?”, all 264 openFDA device enforcement records for recalling firms located in China, 28 August 2026. https://currawongweb.com/research/#fda-enforcement Dataset: https://doi.org/10.5281/zenodo.23298993
BibTeX
@dataset{currawong_fda_china_device_enforcement_2026,
author = {Bao L. Zhou},
title = {{US device enforcement records for recalling firms located in China: concentration, status and age}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.23298993},
url = {https://doi.org/10.5281/zenodo.23298993}
}
This study reports the shape of a public enforcement record. It is not an assessment of any manufacturer, and Currawong does not certify suppliers.
Registration fields: capital, status and scope
Original study46 query inputs · three fields
Capital, status and scope: what the returned fields show
A large capital figure, active status and manufacturing wording do not clear a supplier. We checked what a commercial platform returned for 46 selected entries. The results show field values, not bank balances or factory capacity.
Capital, status and business-scope findings
Paid-in and subscribed values compared across 46 platform records, queried on 28 August 2026.
What the record shows
Entries
Share
Paid-in value present and equal to the subscribed figure
16 of 46
34.8%
Paid-in value present and below the subscribed figure
13 of 46
28.3%
Paid-in field empty
17 of 46
37.0%
Shareholder-contribution entries returned
18 of 46
39.1%
We checked 46 query inputs (45 18-character strings and one 8-character string). Numeric CNY subscribed capital appeared in 44 entries, ranging from ¥100,000 to ¥1,023,855,833 with a median of ¥9,000,000. The 15 numeric empty-paid-in entries had an average founding year of 2017 and a median of ¥3,000,000. The 29 populated entries averaged 2011 with a median of ¥20,000,000. Status returned three stored labels (存续 26, 开业 19, 仍注册 1) across 11 company-type strings (10 after bracket folding). Business-scope text had a median length of 193 characters and a maximum of 591, with 30 of 46 (65.2%) carrying licensed/general-project markers. Scope strings matched sale/trade terms in 45 of 46 (97.8%), manufacturing terms in 39 of 46 (84.8%), and both in 39 of 46. Trade-only appeared in 6 of 46 (13.0%), import-export in 36 of 46 (78.3%), and manufacture without trade in 0 of 46 (0%). Full tables, method limits and statutory official sources: Registered capital, status and business scope study.
Citing the registration-field study
Row-level and summary files: CSV · JSON (8 September 2026 median note on the standalone page).
Currawong, “China scope records: 0 of 46 mention manufacturing without trade wording”, returned fields for 46 selected commercial-platform query inputs, 28 August 2026. https://currawongweb.com/verify/registered-capital-business-scope-china/ Dataset: https://doi.org/10.5281/zenodo.22145056
BibTeX
@dataset{currawong_registration_field_meaning_2026,
author = {Bao L. Zhou},
title = {{What Chinese registry fields guarantee: paid-in capital, registration status and business scope across 46 manufacturers}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22145056},
url = {https://doi.org/10.5281/zenodo.22145056}
}
This study reports properties of registry fields. It is not an assessment of any company, and Currawong does not certify suppliers.
Public risk signals across 46 query inputs
Original studysix record types · 46 query inputs
An empty risk screen does not clear a supplier.
Check what each result says and which source returned it. On 28 August 2026 we queried six record types for 46 entries from an earlier manufacturer lookup. This measures platform responses. It does not measure supplier safety or the best order of checks.
What the platform returned
Records returned for 46 query inputs. All 276 responses were classified as readable. Queried 28 August 2026.
Signal
Entries
Share
Has a published court hearing notice
17 of 46
37.0%
Subject to enforcement
4 of 46
8.7%
Listed as a dishonest judgment debtor
1 of 46
2.2%
On the abnormal-operations directory
0 of 46
0%
On the serious-violation list
0 of 46
0%
Named in a tax-arrears notice
0 of 46
0%
Twenty-eight entries (60.9%) were classified as no-record across all six types. Of the other 18, 14 had one type present and 4 had two. Among entries with hearing notices, the stored count had a median of 3 and a maximum of 52. The original responses were not retained, so the file cannot show whether each count was a total or a returned page count.
How to use these results
Read the result with its source and date. A platform returning no record does not establish that the official source has none. A returned record needs its details checked; its presence alone does not settle the question about your supplier.
Frequency does not set priority. Hearing notices were the most common result in this file. We did not measure whether they helped buyers more than other records. Choose checks for the question you need to resolve, rather than for how often they returned data in this group.
These counts do not predict recovery. We stored no amounts, case outcomes or transaction results. The data cannot tell you whether a creditor recovered money, whether a company can pay, or what would happen in your dispute.
Method, and what this study cannot say
Six company-level interfaces on a commercial business-information platform were queried once per entry. The 46 entries came from earlier searches that returned one candidate with a non-empty code field.
45 query strings were 18 characters long; one was an 8-character string. That entry returned no-record for all six types. Length alone does not verify the other entries. We retain the original denominator of 46 rather than silently changing the historical results.
Only counts and presence were stored. No case numbers, parties, amounts or individual names were recorded, and no person-level interface was queried. All 276 stored results were classified as present or no-record; none was marked unreadable.
The parser treated the platform's no-result code and a successful null result as no-record. It used a total when supplied; otherwise it counted returned array entries. An empty top-level array would be labelled present with a count of zero, although that combination does not occur in this file. Without the original responses, we cannot recheck which response shape produced each stored result.
The original write-up also cited two positive-control queries. Their responses are not included in this dataset, so those counts cannot be independently checked from this download. A successful control would not prove that every other result was complete.
What it cannot say
Zero of 46 does not mean zero in the population. This selected group does not establish a population rate. Do not read it as "this never happens".
The platform is not the official register. A platform holding no record is not proof the government register holds none.
Absence never clears a supplier. The returned data do not establish supplier safety.
One industry, one day. The frame came from a trailer-manufacturer lookup. It is not a representative sample of Chinese suppliers.
A hearing notice is not a verdict. It records that a case was scheduled, not who was right, and not whether the company was plaintiff or defendant.
Citing the base-rate study
Correction, 8 September 2026: we corrected how the query inputs were described and removed conclusions about check priority and recovery. The figures are the original measurements. The downloadable files and archive title below still show the earlier wording; read them with the corrected method and limits above.
You may quote or reproduce these figures, including commercially, provided the measurement date, the frame and the stated limits travel with them. One row per queried entry, with the six per-signal states and counts, is in the result file (JSON). No case details or individual names appear in either file.
Archived copies, each with its own DOI, resolving independently of this site: Zenodo · Harvard Dataverse.
A citation with everything it needs:
Currawong, “An empty risk screen does not clear a supplier”, six commercial-platform record types across 46 selected query inputs, 28 August 2026. https://currawongweb.com/research/#risk-signal-base-rate Dataset: https://doi.org/10.5281/zenodo.22145063
BibTeX
@dataset{currawong_public_risk_signal_base_rate_2026,
author = {Bao L. Zhou},
title = {{Base rate of six public risk signals across 46 Chinese manufacturers}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22145063},
url = {https://doi.org/10.5281/zenodo.22145063}
}
This study reports how often six platform record types were returned for the selected query inputs. It is not an assessment of any company, and Currawong does not certify suppliers.
English-name lookup: results, method and citations
Original measurement106 companies
Can you find a Chinese supplier from its English name?
Use an English name to find candidates, then check the Chinese registered name and business licence. On 12 August 2026, we compared search results for 106 China-listed trailer makers from NHTSA vPIC. A matching English-name field was a lead to check, not proof of identity.
Measured 12 August 2026 · Frame: 106 China-listed trailer manufacturers in NHTSA vPIC · Prepared by Bao L. Zhou, Currawong’s China-side verification desk.
English-name lookup: key counts and brand comparison
Measure
Result
Of
Returned at least one candidate
57.5%
61 of 106
: top candidate has an English name on its registration record
83.6%
51 of 61
: that recorded English name equals the input
77.0%
47 of 61
: top candidate carries an 18-character Unified Social Credit Code
83.6%
51 of 61
All inputs: top result has a matching English-name field
44.3%
47 of 106
Twenty-two entries in the frame carried both a full English name and a short or brand name. Full-name searches returned a candidate in 59.1% (13 of 22), while brand or short-name searches returned a candidate in 90.9% (20 of 22). More returned candidates do not mean more accurate matches, because short names collide across unrelated companies. Ask for the supplier’s business licence (营业执照) to turn a name search into an exact 18-character code lookup. Full method notes, brand-collision breakdown and FAQ: Can you find a Chinese supplier from its English name?
Citing the English-name study
Machine-readable metrics: CSV (frame from our NHTSA vPIC census via the vPIC API; wording note of 8 September 2026 on the standalone page).
Currawong, “Can you find a Chinese supplier from its English name?”. 106 China-listed trailer manufacturers from NHTSA vPIC searched by the name held in that register from a mainland egress, two same-platform runs, 12 August 2026. https://currawongweb.com/verify/find-chinese-company-by-english-name/ Dataset: https://doi.org/10.5281/zenodo.22933140
BibTeX
@dataset{currawong_english_name_lookup_2026,
author = {Bao L. Zhou},
title = {{English-name lookup rates for Chinese manufacturers (NHTSA vPIC frame, August 2026)}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22933140},
url = {https://doi.org/10.5281/zenodo.22933140}
}
This study reports rates, not a service claim. Currawong verifies public records on request and states sources, query dates and limits with every result; it does not certify suppliers.
Machine translation: second-model review
Engineering practice, not a buyer decision98 strings · 15 languages
One model translated. Another one checked.
A second model flagged 11 of 98 strings after they passed the text checks. We then edited eight strings and kept three with notes on the choice. The flags do not tell us the true error rate.
Reviewed 12 August 2026 · Frame: 98 interface strings across 15 languages, two rounds · Prepared by Bao L. Zhou, Currawong’s China-side verification desk.
Machine-translation review: the numbers
Measure
Result
Of
Strings flagged for review
11.2%
11 of 98
: wrong domain term
45.5%
5 of 11
: grammar, voice or collocation
27.3%
3 of 11
: meaning close but not exact
27.3%
3 of 11
Flags classified as high severity
9.1%
1 of 11
Flags our automated checks caught first
0%
0 of 11
Flags occurred in six of the 14 non-English languages: Arabic, Vietnamese, Hungarian, Russian, Polish and Portuguese. Eight languages had no flags. English was also included in the 15-language frame. These small counts do not rank language quality or establish that unflagged text was correct.
The document-term flag
One reviewed string asked a buyer to request a photo of the Chinese business licence (营业执照) when a search returned nothing. The licence was the intended document.
The reviewer interpreted the Arabic wording as “work permit”. The dated summary classified this as the one high-severity flag.
If the reviewer was right, a buyer could ask for the wrong document. We did not test that with buyers or measure harm. The text passed the character and length checks. Those checks did not settle what the term meant.
The write-up also raised doubts about Hungarian and Polish terms. The public file gives totals. It does not show the strings or a native speaker’s verdict. Readers cannot check each language claim from this file alone.
Why the automated gates missed all eleven
The recorded workflow used four checks before model review:
Completeness: every string present in every language, so no reader silently falls back to English.
Script and diacritics: check the expected characters and accents.
Forbidden wordings: a per-language list of claims we must never make. Examples: calling an unconfirmed candidate a verified supplier, or calling an outage a company that does not exist.
Length: apply a per-string budget. Rendered layout still needs a browser check.
The original write-up records two failure probes: stripped Turkish diacritics and an injected forbidden phrase caused their respective checks to fail. These probes test those rules, not translation accuracy.
The rules did not flag these 11 strings. That does not mean code can never find the same issues. A new rule could check a known term. That rule would still need to be tested.
Keep text checks and meaning review separate. A string can pass the configured rules and still need its meaning checked.
Method, and what this study cannot say
One model translated the text. A different model received each string and its intended English meaning, then back-translated and flagged concerns. It did not see the first model’s reasoning. We classified the flags and recorded corrections or accepted drift.
A different model gives a second pass. Both models may share the same mistakes. The reviewer saw the intended meaning, so this was not a blind test or a check against a trusted translation.
The 12 August record says we changed eight strings and kept three with notes. For one status term, the suggested new word had not been checked. These counts describe that day’s work. They do not show what the live site says today.
What it cannot say
It is not a benchmark. 98 short, domain-specific interface strings, one translating model, one reviewing model, one review date. It measures a workflow, not machine translation as a field.
Neither model is a native speaker. The reviewer flagged what it could see; it also stated plainly that it could not find authoritative sources for some phrases it was judging. Its flags are findings to investigate, not verdicts.
11.2% is not a verified error rate. The reviewer could miss errors or flag words that were fine. There was no trusted reference for every string. The count gives neither a lower nor an upper bound on the true error rate.
The per-language split proves nothing. Six languages with flags and eight without, at one to three flags each, is not evidence about those languages.
This covers our own text. The review did not include native-speaker validation. The editorial policy explains the machine-assisted language boundary.
Citing the machine-translation review
Wording corrected 8 September 2026. Counts and the review date are unchanged. “Independent” in the archive title is the name of the old deposit. It does not prove that the models made errors on their own. The public CSV gives totals; it does not list each string.
You may quote or reproduce these figures, including commercially, provided the review date, the frame and the stated limits travel with them. Machine-readable metrics with numerators and denominators are in the result file.
Corrected archive copies with unchanged counts, published 11 October 2026: Zenodo v1.1.0 · Harvard Dataverse v3.0. Earlier versions remain available. Use a corrected copy for new citations.
A citation with everything it needs:
Currawong, “One model translated, another checked: 11 of 98 flagged”, second-model review of 98 interface strings across 15 languages in two rounds, 12 August 2026. https://currawongweb.com/research/#machine-translation-review Dataset: https://doi.org/10.5281/zenodo.23298957
BibTeX
@dataset{currawong_machine_translation_review_2026,
author = {Bao L. Zhou},
title = {{Independent back-translation review of machine-translated interface text (98 strings, 15 languages, August 2026)}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.23298957},
url = {https://doi.org/10.5281/zenodo.23298957}
}
This study reports what one review found in our own interface text. It is not an assessment of any named translation product, and it is not advice on whether to use machine translation for regulated content.
RIPE Atlas: network reachability of official portals
Original study50,248 observations · 621 probes · 32 countries
Told to check the official registry: can a buyer outside China reach it at all?
Buyers are routinely told to confirm a Chinese supplier against the official registry before paying. That advice quietly assumes the portals answer from wherever the buyer happens to be. We measured whether they answer at the network layer: eight official portals and two controls, from 621 RIPE Atlas probes in 32 countries outside mainland China, continuously for fourteen days.
What answered, and what did not
Every observation between 26 August and 9 September 2026, grouped by measurement type. Controls are www.gov.cn and www.baidu.com.
Measurement
Eight official portals
Share
Two controls
Share
DNS resolution
13,531 of 13,531
100.0%
3,386 of 3,386
100.0%
TLS handshake completed
12,785 of 13,306
96.1%
3,213 of 3,251
98.8%
ICMP ping answered
8,123 of 13,315
61.0%
3,447 of 3,459
99.7%
DNS and TLS put the official portals within a few points of two hosts nobody claims are hard to reach. The ping column is the one that looks alarming, and it is the one that misleads.
Per portal: whether it answered ICMP, against whether its TLS listener completed a handshake, over the same probes and the same window.
Portal
ICMP ping answered
TLS handshake completed
www.gsxt.gov.cn National Enterprise Credit Information Publicity System
1,592 of 1,658 (96.0%)
1,623 of 1,726 (94.0%)
www.creditchina.gov.cn Credit China
1,718 of 1,726 (99.5%)
1,606 of 1,679 (95.7%)
wenshu.court.gov.cn China Judgements Online
0 of 1,703 (0.0%)
1,629 of 1,641 (99.3%)
zxgk.court.gov.cn Enforcement Information Disclosure
0 of 1,621 (0.0%)
1,531 of 1,618 (94.6%)
credit.customs.gov.cn Customs enterprise credit
1,608 of 1,667 (96.5%)
1,534 of 1,658 (92.5%)
sbj.cnipa.gov.cn CNIPA trademark office
1,577 of 1,580 (99.8%)
1,563 of 1,623 (96.3%)
openstd.samr.gov.cn SAMR national standards
0 of 1,650 (0.0%)
1,632 of 1,691 (96.5%)
cx.cnca.cn CNCA certification lookup
1,628 of 1,710 (95.2%)
1,667 of 1,670 (99.8%)
Three hosts answered no ping at all: 0 of 4,974 attempts. They are both court portals and the national standards portal. Over the same fourteen days, from the same probes, those three kept completing the TLS handshake, at the per-host rates in the table above. The absent ping is an ICMP policy on the host or its path. It is not evidence that anyone cannot reach them.
This matters beyond these three hosts. A reachability check built on ping alone would have reported three of eight official portals as unreachable while their TLS listeners were answering throughout. Anyone quoting a ping-based figure about Chinese government hosts should say which layer it came from.
Method, and what this study cannot say
Thirty-one periodic RIPE Atlas measurements ran over ten hosts, eight official portals and two controls. They used the ping, TLS certificate and DNS measurement types, from 26 August 2026 at 11:29 UTC to 9 September 2026 at 05:42 UTC. 50,248 result rows from 621 probes in 32 countries, none of them in mainland China. Every row carries its measurement id, probe id, probe country and timestamp. The measurement definitions stay public, so anyone can re-read them from the RIPE Atlas API and recompute every figure above.
Success is defined per measurement type and stated in the file: at least one packet received for ping, a completed handshake for TLS, at least one answer for DNS. For DNS rows the queried hostname is joined in from the measurement definition, because a RIPE Atlas DNS result does not repeat it. No content was fetched from any portal. These are ping, TLS-handshake and DNS measurements only. Nothing here was obtained by scraping, proxying, or working around an access control.
What it cannot say
Reachable is not usable. This says nothing about whether a page renders, whether a search returns a result, or whether a CAPTCHA or a login stops a person. Our separate browser-level measurement of the same portals found most front pages refused on its test date. That is a different layer and a different method. The two figures must never be quoted as one.
It does not establish intent. A failed observation may reflect routing, filtering, server-side rate limiting, conditions at the probe, or an ordinary outage. We report what the probes saw.
The probes are not a sample of anything. RIPE Atlas probes are largely volunteer-hosted on residential connections. Placement is not random, and no country-level statistic should be read out of this file, however tempting the 32-country spread looks.
It expires. Measurements stopped on 9 September 2026. Reachability changes; every row carries its own timestamp for that reason.
Absent ICMP is not absent service, as three of these eight portals demonstrate. Nor is the reverse true: a completed handshake does not mean the service behind it will answer a query.
Citing the network-reachability study
You may quote or reproduce these figures, including commercially, provided the measurement window, the layer measured and the stated limits travel with them. Every observation, one row each, is in the CSV (JSON, which also carries the per-host summary the tables above are computed from).
Archived copies, each with its own DOI, resolving independently of this site: Zenodo · Harvard Dataverse.
A citation with everything it needs:
Currawong, “Told to check the official registry: can a buyer outside China reach it at all?”, 26 August to 9 September 2026. Network-layer reachability of eight Chinese official portals, measured from 621 RIPE Atlas probes in 32 countries. https://currawongweb.com/research/#atlas-network-reachability
BibTeX
@dataset{currawong_china_portal_network_reachability_2026,
author = {Bao L. Zhou},
title = {{Network-layer reachability of eight Chinese official due-diligence portals from outside mainland China (RIPE Atlas, 26 August to 9 September 2026)}},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22681948},
url = {https://doi.org/10.5281/zenodo.22681948}
}
Measurements were funded by RIPE Atlas research credits under ticket #1094691; publishing the resulting dataset was a condition of that grant. This study reports network-layer observations. It is not an assessment of any portal operator, and it does not show that any portal is usable or unusable for a given task.
Frames are stated, not implied. The saved 264-name frame is attributed to three provincial lists in the original notes. The Shandong attachment is missing, and full list-to-name verification remains open. This is a selected group. Its rates do not estimate all Chinese suppliers or set bounds for other groups. Selection for a programme does not prove a firm is safe to trade with.
Registration data was read through licensed commercial data platforms that republish filings originating in the National Enterprise Credit Information Publicity System; person-name fields were discarded at collection. An absence on a platform is not proof of absence in the official record.
Access results belong to their test conditions. Later overseas requests used partly paired target and control nodes, as the registry study explains. They do not show why a request failed or whether a buyer can complete a search today.
Which file version did you use?
Download the file-version manifest (JSON) and keep it with your data. It lists each English research dataset, its study page, observation period, method and reuse terms. Each site download has a byte count and SHA-256 checksum. Compare that checksum with your saved file to check whether the bytes match.
The page version and the observation period are separate. An edit to a report does not mean the data was collected again. The manifest also records a content fingerprint for each report page. This follows our site's content-version rules; it is not a checksum of the raw HTML.
Archive links come from the current study pages. Their status in this manifest is NOT_CHECKED: it does not check whether an archive is reachable or which archived version matches the site file. A DOI and a matching checksum do not prove that a measurement is correct. These are public research assets; they do not show that a customer has been served.
Citing this research
You are welcome to quote or reproduce these figures, including commercially, provided the observation date and the stated limits travel with them. The dates are load-bearing: citing a rate or status code without its date misrepresents it. Link the study page rather than this index so readers reach the method and limits.
The English-name lookup study has its own page. The machine-translation review is an anchored section of this index; link directly to #machine-translation-review. Each study page carries machine-readable Dataset metadata; the contact routes are here for method clarifications.
These pages report measurements, not legal conclusions, audits or safety findings, and none of them evaluates any specific supplier a reader is dealing with. For a specific supplier: the free in-browser screen or a dated China-side record check.
If you want these records pulled for your own supplier: the “Just check who they are” selection of the report menu covers them, with packs from $26.55. First paid order: unhappy for any reason, tell us within 14 days of delivery and it is refunded in full. The delivery window shown with the order is the one that applies. Buying from a Chinese seller of record is a separate route, with its own terms.