Verification: Building Trust on 44Net
When we use 44Net, we are part of a network operated by and for genuine radio amateurs, dedicated to learning, experimentation, and non-commercial development. We trust one another to use this resource in ways that uphold these values. As the operators of 44Net, we also represent the amateur radio community to the broader Internet, which trusts us to manage 44Net responsibly. This policy guide explains how building and maintaining trust enables you to do more with 44Net and helps protect it as a valuable resource.
Verification Benefits
A user can access much of what 44Net offers with just a verified license. In addition, a user who also has a verified location can request up to 254 IPs, a /24 subnet, BGP authorization, and more.
This table compares what a user can get with each level of verification:
| Email Verified | Email and License Verified | Email, License, and Location Verified | |
|---|---|---|---|
| Portal Access | ✔️ | ✔️ | ✔️ |
| Portal Support | ✔️ | ✔️ | ✔️ |
| Maximum Total IPs | 127 | 254 | |
| Largest Subnet | /25 | /24 | |
| Multiple Subnets | ✔️ | ✔️ | |
| DNS Services | ✔️ | ✔️ | |
| IPIP Mesh | ✔️ | ✔️ | |
| BGP Authorization | ✔️ |
Privacy Protections
A user who values privacy is not alone on 44Net. ARDC takes privacy seriously and implements multiple security and privacy protections as part of user verification processes:
- Before submitting documents, users may obscure or redact information that is not required for verification.
- Files uploaded for verification are kept private to the user and the ticket handler during the verification process.
- The contents of ticket messages and attachments are kept within the system and not exchanged externally (such as via unsecured email).
- When verification is complete, personal data associated with the verification request is deleted, including messages and uploaded documents.
- Staff and volunteers who handle tickets must sign confidentiality agreements committing to the protection of personal information encountered in the course of their work, before undergoing training and certification to process user verifications.
ARDC publishes a privacy policy describing its personal information practices, including compliance with relevant laws:
[1](https://www.ardc.net/about/legal/website-privacy-policy/)
Verification Requirements
A user begins verification by registering on the portal and submitting a verification request together with supporting documents. ARDC staff and authorized 44Net volunteers then follow procedures in the portal to process the request. If the provided documents are acceptable, the request will be approved. If not, the request will be rejected, and the user may submit the request again with different or additional information.
A user may decline to upload official documents and instead request to join a video call with ARDC staff to present documents on camera.
The procedure for requesting verification as part of portal account setup is documented on the 44Net wiki:
[2](https://wiki.ampr.org/wiki/Portal_intro)
General Requirements
Verification of a license or address requires reliable documents that link the user to their callsign or location. These documents should be uploaded to the portal along with the verification request. The portal accepts files in PNG (.png), JPEG (.jpg), and PDF (.pdf) formats.
License Verification
Protecting the use of 44Net for acceptable amateur radio purposes, including learning, experimentation, and development, calls for ensuring its users are duly licensed amateur radio operators. Providing proof of a valid amateur radio license is a simple and direct way to do this.
The license must specifically authorize the operation of an amateur radio station. Licenses for other purposes, such as equipment ownership or listening only, are not sufficient.
An amateur radio operator’s license must be current, valid, and issued by the authority having jurisdiction in the operator’s region. License documents should show the following information:
- User’s name
- User’s callsign
- Expiration date, if applicable
- Issuing authority
Examples of an acceptable license document may include:
- An official copy of a license in PDF format
- A digital photo of a printed license card
- A scan of an official letter of callsign assignment
- A screenshot of a user profile on a government licensing portal
Best Available Document
Licensing practices for amateur radio operators vary significantly across jurisdictions and can change over time. As a result, there is no single form of license documentation that applies universally. To verify users, we rely on the most authoritative documentation available from each region’s licensing authority.
If a licensing authority provides an official document—such as a license card, certificate, or digital record—users must submit that official document for verification. Where such a document is unavailable or lacks sufficient information, users should provide any other communication issued by the authority that confirms their licensing status, such as an email, letter, or registration notice.
In regions where documentation is unavailable or unreliable, volunteers and staff will work with users to verify a license using multiple reliable secondary sources, such as a verifiable profile on QRZ.com, confirmed QSOs recorded in Logbook of the World, or a page on a club website.
However, no single third-party source—whether a public database or a community-driven site—is sufficient on its own. Publicly accessible databases, including government registries, can be exploited for impersonation, and user-submitted information on community sites may be manipulated. Such sources may be used, but only to corroborate information from other reliable secondary sources.
Location Verification
Maintaining the integrity of the global Internet is essential to 44Net’s reputation and its effective collaboration with other network operators. Verified location information not only ensures that a user is properly licensed to operate in their region but also helps prevent abuse and demonstrates a commitment to the principles that help our community thrive.
To access certain advanced capabilities, such as announcing a 44Net subnet via BGP, a user must provide a physical address that corresponds to their licensed region. This address does not have to be residential, and it will not be published, shared, or used beyond the purposes of verification. It must, however, verifiably link to the user and reflect their licensed region.
Acceptable location verification documents should show:
- User’s name matching the name on the verified license
- A physical address within the licensed region
- The name of the organization issuing the document
Examples of acceptable documents may include:
- Government-issued identification, such as a driver’s license or passport
- A bill or statement from a recognizable public institution, such as a utility company, bank, or insurance company
- A letter from a recognized organization, such as a radio club, confirming the user’s location
Verification Frequency
Users are generally required to verify their license or location only once. However, it is each user’s responsibility to ensure that their license and location information remains accurate and up to date in the portal, and to request re-verification whenever there are significant changes to their license, callsign, or region of operation.
In some cases, users may be asked to re-verify their information, such as if a complaint is received or if mismatches or omissions are identified. Such measures help maintain trust in 44Net and ensure its continued secure and responsible operation.
Organizations
The portal allows users to create organizations, which can have members, callsigns, subnets, and other resources assigned to them. Organization administrators can request resources on behalf of the organization and manage the allocation of those resources to organization members.
Verification requirements for organizations align with those for individuals:
- Callsigns assigned to an organization must be verified, just as for an individual user.
- Location verification is required to request certain resources, such as BGP authorization or a subnet /24 or larger.
- An organization itself does not require a license, but its callsigns and locations must meet the same verification standards as individual users.
Additionally, the organization’s administrators are responsible for:
- Ensuring the organization’s information remains up to date in the portal
- Maintaining compliance with all applicable policies
- Completing individual verification before requesting resources for the organization, as if requesting those resources for personal use
Every member of an organization, including its administrators, must create an individual account in the portal, accept the end-user license agreement, and complete any required verifications before creating or joining an organization.
Sub-users
A sub-user is an individual who does not have a portal account but for whom resources are managed by a verified user. Examples include students, club members, or individuals managed by a regional coordinator.
When managing resources on behalf of sub-users, the verified user assumes full responsibility for how those resources are used. This includes:
- Compliance with all policies
- Responsible use of 44Net resources
- Use of 44Net resources only for their intended purposes
- Providing support for sub-users
Whenever practical, a sub-user should create an account on the portal, complete any required verification, and access managed resources as a registered user, whether individually or as part of an organization.
Support
If a user has questions or encounters issues during the verification process, help is available. Common challenges include navigating the portal, uploading files, or addressing unique situations not covered here.
Before reaching out, users are encouraged to review this guide and FAQs, which cover many common scenarios. A user who would like further assistance should submit a request through the portal’s ticket system, including as much detail as possible to help address the concern.
Verification support is provided by volunteers and staff on a best-effort basis and may not be available 24 hours a day, seven days a week. If an issue is not resolved within a reasonable period of time, a ticket may be escalated for further response.
Next Steps
These verification processes are designed to be straightforward and supportive, not burdensome or a challenge to a user’s trustworthiness. These steps are intended to help ensure that 44Net remains a trusted resource by and for genuine amateur operators pursuing learning, experimentation, and non-commercial development.
Completing verification demonstrates a shared commitment to protecting 44Net as a trusted and valuable resource for the amateur radio community and the broader Internet.
Once verified, you’re ready to explore, discover, and build new things with 44Net.
Frequently Asked Questions
Why do I need to verify my license or location?
Verification helps ensure that 44Net remains a trusted resource for amateur radio operators and supports a shared commitment to using 44Net for its intended purposes of learning, experimentation, and non-commercial development.
Who handles verification?
Verification is handled by “ticket handlers,” staff and volunteers who have completed training, signed a confidentiality agreement, and been authorized to process verification requests.
How long does verification typically take?
Verification is typically handled within a few days, depending on the volume of requests in the queue, the complexity of the verification needed, and the availability of ticket handlers.
Why are established users asked to verify?
Longstanding users have been a part of some of the most significant developments in 44Net’s history. As these users probably know, the procedures now in place to process and record user verifications are more robust than any that 44Net has ever had. With this in mind, the community asks each of its users, including its longstanding users, to verify their license and/or location to help ensure the system is as complete, accurate, and reliable as it can be.
Why does a user verified in April 2024 have to verify again?
As part of the portal update in 2024, existing users were granted provisional, temporary verification status to help smooth the transition to the new system. As each user’s provisional verification expires, the system sends a notification prompting the user to get properly verified.
What if my licensing authority does not issue physical licenses?
If your licensing authority does not provide physical or downloadable licenses, you can provide any official communication or documentation that verifies your callsign and operating privileges. Ticket handlers can also work with you to identify alternative verification methods.
What happens if my verification request is rejected?
In general, “rejected” does not necessarily imply that anything was invalid, only that the specific request could not be closed as “resolved” or “accepted.” If your request is denied, you should receive an explanation of the reason and guidance on submitting additional information.
What should I do if my information changes after verification?
If your license, callsign, or region changes significantly, you should update your information in the portal and request re-verification.
Can I verify more than one callsign?
Yes. Submit a separate verification request for each callsign.
Can I verify more than one location?
If location verification is required, a user should be associated with only one location at a time. A group of users should each have their individual locations verified separately. An organization with an established location may also have its location verified, such as a meeting space or mailing address.
Can I create an organization without being verified?
Yes, but verification is required for callsigns assigned to the organization or to request resources like BGP authorization.
Who is responsible for managing resources in an organization?
Organization administrators can request resources to be allocated to the organization, and can then manage further allocation of those resources to other organization members. Verification requirements apply to organization administrators and members just as for any other user.
Can an organization or other user manage resources on behalf of a user who is not verified?
Yes, but the verified user managing those resources assumes full responsibility for how those resources are used. The verified user is accountable for ensuring that any non-verified users comply with 44Net policies and use resources responsibly.
I disagree with how a verification request was resolved. What can I do?
A user with concerns about how a verification request was handled or resolved can submit a help request ticket through the portal for assistance from ARDC staff.
What about a situation not covered here?
Support is available for situations not covered by existing policy, guidelines, and procedures. A user with a unique situation should submit a help request ticket through the portal. ARDC staff will work with the user to address concerns or help find a solution.