Searchable Interfaces for Verifying Employer Visa Sponsorship Records

Employer visa sponsorship records answer two different questions. DOL LCA disclosure data shows what an employer attested it intended to offer, while the USCIS H-1B Employer Data Hub shows petition decisions. Effective research uses both, then checks the live role.

Why the two public systems exist and what problem each was built to solve

The two databases exist because they record separate events in the sponsorship process. The Department of Labor receives an employer’s Labor Condition Application, filed on Form ETA-9035/ETA-9035E before an H-1B petition reaches USCIS. That application records what the employer attests about the job title, worksite, offered wage, and prevailing wage. Certification permits the employer to proceed toward a petition. It does not establish that the employer took that next step.

USCIS records what happens next, the decision on the petition. Its records concern approvals, denials, and withdrawals by petition type rather than the employer’s initial description of the proposed job. The distinction is between intent attested and decision rendered. Neither dataset publishes a unique key connecting a specific LCA to a specific petition, so the two systems cannot produce a perfect filing-to-hire trail.

What the USCIS H-1B Employer Data Hub actually contains and how to query it

The Hub’s most useful distinction is between new employment and other petition types. Its breakdown separates new employment, continuation of previously approved employment without change, change with the same employer, new concurrent employment, change of employer, and amended petitions. Those categories are not interchangeable measures of hiring. Only new employment approvals confirm sponsorship of workers who were not already inside the H-1B system. For a candidate seeking that route, a large total approval count can therefore be less informative than a much smaller column within it.

Continuing approvals answer a different question about the employer. High renewal and extension activity relative to new employment approvals signals that a company retains H-1B workers over time, but may not be actively bringing in new hires. Approval and denial counts also need to be read together. Comparing them across two or three recent fiscal years helps distinguish a high-volume filer with a strong adjudication record from one with a troubled record. Volume alone does not supply that distinction.

USCIS documentation describes coverage from FY2009 through FY2026 Q3, with searches by employer name, state, city, ZIP code, and two-digit NAICS code. Results can be exported to Excel or CSV. Records show separate approval and denial columns for each petition type and fiscal year, aggregated by employer identifiers and geography. USCIS identifies employers using the last four digits of the tax identification number, while large companies may file through several legal entities or subsidiaries. Searching the different names helps avoid treating one line in the results as the whole corporate group.

USCIS also specifies how to read the dates and outcomes. The fiscal year is the year of adjudication, and the figures represent first decisions. A search can establish recent petition activity without revealing the exact job behind it. The Hub publishes employer mailing-address geography, but not exact worksites, wages, or job titles, which leaves the candidate’s role-level question unanswered.

What the DOL LCA disclosure data contains and how it answers different questions

DOL disclosure data has the job details that the Hub leaves out. It becomes the more useful source when the question is whether an employer has filed for a particular occupation, in a particular city, at a wage relevant to the candidate’s seniority. A company that sponsors engineers may never have filed for accountants, even if both occupations appear on its careers page. The useful match is between the filing and the candidate’s intended work.

DOL’s Office of Foreign Labor Certification publishes quarterly disclosure files for LCA, PERM, H-2A, H-2B, CW-1, and Prevailing Wage programs. The LCA files cover H-1B, H-1B1, and E-3 applications, and the same disclosure platform has separate program files for PERM. This public-record system predates the Hub. In practice, the search starts with an employer name and narrows by SOC code or job title, city, state, and reporting period. PERM records show evidence of permanent-residence sponsorship, so the search can go beyond temporary status.

Wage fields also have a forward-looking use. The DHS final rule published at 90 FR 60864, effective February 27, 2026, replaced the random draw with a wage-weighted lottery. Under that rule, a registration at Level I counts once, while one at Level IV counts four times. An employer’s wage-level distribution thus helps candidates judge their chances in the lottery as well as the employer’s past plans to hire. The distribution is informative because the offered wage’s qualifying level changes the registration’s weight.

DOL’s FLAG Case Status Search serves a narrower purpose than the disclosure files. Given a specific LCA case number, it can show whether the case is certified, withdrawn, denied, or still in process. The search checks a filing detail already in hand, while the disclosure files support searches for plausible sponsors.

The structural limitations both systems share and why they require cross-checking

An LCA may never lead to a petition, and a filed petition may not be approved. These records, including approvals, are the most reliable evidence available for the events they document, with an open job and an employer’s willingness to sponsor a particular applicant requiring separate evidence.

Raw filing counts need similar restraint. One LCA can cover several workers, and many applications concern extensions or job changes. Counting LCAs therefore does not count new-hire opportunities. The Hub’s petition-type breakdown helps interpret that activity, while legal-name searches help avoid understating a corporate group’s volume. The same identity problem affects PERM research when related entities appear separately.

Geography and timing introduce two further boundaries. A Hub city may identify the employer’s mailing address rather than the actual worksite, so a metro-specific search needs the LCA location. Historical willingness is also not a current promise. Employers can revise sponsorship policies, and consistent filings in earlier fiscal years may precede a change after fee increases or budget shifts in 2025–2026.

A practical cross-check workflow from employer history to role-level evidence

The practical sequence begins in the Hub. Search the employer’s name and focus on new employment approvals in the most recent two or three fiscal years, noting denials relative to approvals. Search related legal entities as well. Exporting results to CSV helps when several entities need comparison. This first pass establishes the petition history before time goes into researching individual jobs.

Next, search the same employer in DOL LCA disclosure data. Try legal-name variants, including “Inc.”, “LLC”, and subsidiary names, then narrow by the candidate’s SOC occupation code and target city or metro. Confirm the worksite here. Read the wage-level distribution as well as the job title. Filings clustered at Level I or II signal different lottery prospects from those clustered at Level III or IV under the wage-weighted system.

The third step applies when permanent-residence sponsorship is important. Search the separate PERM files on the same DOL disclosure platform for the employer and its related legal names. Consistent PERM activity together with H-1B LCAs signals a more complete sponsorship infrastructure. It adds a longer-term dimension to the shortlist. It does not replace the role-level checks that follow.

Fourth, read the live posting for clear wording on sponsorship. “H-1B sponsorship available” and “visa transfer supported” are positive signals, although they describe different possibilities. “Must be a U.S. citizen or permanent resident” and “no visa sponsorship” are exclusionary signals. A promising database result is not a reason to treat the current posting as a clerical inconvenience.

Finally, ask the recruiter whether the role qualifies for new employment H-1B sponsorship or only H-1B transfers. Request the legal petitioner name so it can be cross-referenced with the records, and confirm cost responsibility in writing. Specific questions make the final check more useful. If the lottery is the bottleneck, a separate search for cap-exempt employers is also worthwhile. Institutions of higher education, nonprofits affiliated with them, and research organizations that qualify can offer cap-exempt roles under INA 214(g)(5) and the DHS H-1B modernization rule effective January 17, 2025.

The March 2026 USCIS Hub outage and what it revealed about data access risk

The March 2026 Hub outage exposed a practical weakness in depending on one interface. The Hub lost its search tool, interactive map, and downloadable datasets for fiscal years 2024–2026. That interruption affected both interactive research and access to recent downloadable records. A workflow can be logically sound yet operationally fragile. When its first source disappears, familiarity with another source becomes more than a useful extra.

DOL’s disclosure files remained intact throughout the outage. OFLC continued publishing quarterly performance data for H-1B, H-1B1, E-3, and other programs, with PERM published separately. Candidates who knew how to search DOL on its own could keep doing research. Those who used only the Hub lost access to recent fiscal years, and an aggregator that drew on the same Hub might not offer another way to reach the data.

The OPEN Government Data Act requires agencies to keep public datasets up to date, but that legal duty does not bring the data back at once. That distinction is especially concrete for a candidate whose OPT clock is running. A deadline does not pause for interface maintenance. Reliable research requires knowing both systems independently and understanding what each can prove. DOL provided a fallback for investigating employer intent and role details.

How a pre-filtered employer database changes the search before either government interface is consulted

The workflow still leaves an earlier question unresolved, namely which employers deserve investigation in the first place. General platforms such as LinkedIn and Indeed surface listings without an indicator of whether the employer has filed an LCA or an H-1B petition. Candidates must supply that missing check themselves. Applied to an unfiltered pool, the process can require hundreds of employer searches that end with no sponsorship history.

A job board limited to employers with documented sponsorship history changes that starting point. When the employer pool is cross-referenced against DOL disclosures and USCIS petition records, discovery begins with a filing signal already present. Verification then tests a shortlist. Candidates still need to check the role, worksite, petition type, and current policy. Pre-filtering removes a class of unsuitable leads without claiming that every remaining vacancy offers sponsorship.

Filing history is a better predictor of new-hire sponsorship than job title, seniority, or company name recognition. For candidates on OPT, CPT, or approaching a visa deadline, that distinction has a direct time cost. Unfiltered discovery can consume weeks waiting for employers that were never going to sponsor. The useful endpoint is a current role whose stated terms align with the employer’s petition history and role-level filings, rather than an impressive employer total with no application worth making.