Begin with the project, not a familiar name
You may find two repositories with similar project names while checking a public release announcement. Write down the project website you already trust, the organization URL you found and the repository URL under review. This prevents an organization badge from being attached in your notes to an unrelated search result.
Open the organization profile itself. A badge captured in a screenshot or mentioned in a README is not the same observation as the current profile. Record the date you checked it and the exact domain shown with the profile information.
Read the domain relationship precisely
GitHub documents its organization badge as a result of verifying ownership of domains. The profile’s displayed website and email information must match verified domains; different domains, including certain variants, require their own verification. GitHub also describes domain approval as a separate procedure. Source
Compare the exact host instead of deciding that every address containing the project name is equivalent. For an illustrative project, docs.example.org and example.org should be written down as different hosts even if the organization operates both. Do not infer the status of one from the spelling of the other.
This is a reading task. You do not need to change DNS, request organization access or verify a domain yourself to inspect a public project source.
Keep three different checks in separate rows
| Object | Useful question | What remains to check |
|---|---|---|
| Organization profile | Which domain relationship is documented? | Whether this is the organization relevant to your task |
| Repository | Is this the project linked by the organization’s own site? | Whether you opened the correct repository and version |
| Release or document | What does the actual passage say? | Whether it supports the particular claim you plan to cite |
A profile can help you navigate to a project without settling the truth of every statement in that project. Likewise, an absent badge is an observation about the profile, not a finding that the organization is fraudulent.
Preserve the evidence you actually used
Follow a project link from the organization’s own website when available, compare its destination with the repository you found, and save the relevant release or document address. If the site and repository disagree, keep both destinations and label the relationship unresolved rather than choosing the more polished page.
For an illustrative changelog check, the useful result is a repository, a release version and the sentence supporting the feature. A badge alone is not that result. Use a stable GitHub source link when the file may change later.
If the badge you saw sits beside a commit, use the commit-signature guide instead. It addresses a different object and should not be substituted for organization-domain review.