Summary
- Registrar
- NameSilo, LLC
- Status
- clientTransferProhibited
- Created on
- July 7, 2013
- Expires on
- July 7, 2027
- Name servers
- ns1.inetbridge.net, ns2.inetbridge.net
- Mail servers
- usb-drivers.org
- SPF
- Soft
- DKIM
- 1 key found
- Website
- See the website
Authorized senders (SPF)
E-mails sent by any other server are accepted but flagged as suspicious.
SPF lists the servers allowed to send e-mails for usb-drivers.org.
| Rule | Value | Result |
|---|---|---|
| ip4 | 162.255.164.58 | Allowed |
| a | — | Allowed |
| mx | — | Allowed |
| all | — | Suspicious |
Top-level DNS lookups: 2 of 10 allowed
Record
v=spf1 ip4:162.255.164.58 +a +mx ~all
E-mail signing (DKIM)
DKIM keys published by usb-drivers.org under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| default | — | RSA 1024 bits · short | Active |
RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.
MX, SPF, DKIM and DMARC: the e-mail records
Four DNS records make a domain's e-mail work. MX says where e-mails sent to usb-drivers.org arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from usb-drivers.org was really sent by this domain, which protects it against spoofing.
MX
An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @usb-drivers.org address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.
Example record
usb-drivers.org MX 10 mx1.usb-drivers.org. usb-drivers.org MX 20 mx2.usb-drivers.org.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.usb-drivers.org.
- Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
- 0 .
- An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.
Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.
SPF
SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).
Example record
usb-drivers.org TXT "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"
What the record contains
- v=spf1
- Identifies the record as an SPF policy. It must come first.
- ip4, ip6
- Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
- a, mx
- Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
- include
- Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
- -all, ~all
- Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).
A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.
DKIM
DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.usb-drivers.org, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.
Example record
google._domainkey.usb-drivers.org TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"
What the record contains
- v=DKIM1
- Protocol version. Optional but recommended, in which case it must come first.
- k
- Key algorithm: rsa, the most common, or ed25519.
- p
- Public key, base64-encoded. An empty value means the key has been revoked.
- t
- Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.
Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.
DMARC
DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.usb-drivers.org, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.
Example record
_dmarc.usb-drivers.org TXT "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"
What the record contains
- v=DMARC1
- Identifies the record as a DMARC policy. It must come first.
- p
- Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
- sp
- Subdomain policy. Without it, subdomains follow the domain's policy.
- rua
- Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
- ruf
- Address that receives detailed failure reports, message by message. Few providers still send them.
- pct
- Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
- adkim, aspf
- DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).
To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.
DNS records of usb-drivers.org
IP addresses (A and AAAA)
An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.
| Type | IP address |
|---|---|
| A | 162.255.164.58 |
Name servers (NS)
NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.
| Server | IP address |
|---|---|
| ns1.inetbridge.net | 162.255.164.58 |
| ns2.inetbridge.net | 162.255.165.58 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @usb-drivers.org addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.
| Priority | Server | IP address |
|---|---|---|
| 0 | usb-drivers.org | 162.255.164.58 |
TXT records
TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.usb-drivers.org.
| Name | Content |
|---|---|
| usb-drivers.org | v=spf1 ip4:162.255.164.58 +a +mx ~all |
| default._domainkey.usb-drivers.org | v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDK9h2krvbGfS51BMK4wSCSXTM87m8jH8/T9ke1LaoAi+WMhSgra1JCEA3ilFKKmJ8ieay3IRNwCGIrurx6rXe7p64t189tY1Uys/o4EU/3/Qj09NQsB5Pzj603VzQA818AbrsxXQDEHXOvxJkqg7Gm5IHgZ3kL9/euO5nDhphRdwIDAQAB; |
Related IP addresses
IPv4 addresses used by usb-drivers.org: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 162.255.164.58 | Website, Name server ns1.inetbridge.net, Mail server usb-drivers.org, Authorized by SPF | 162.255.164.0/24 |
| 162.255.165.58 | Name server ns2.inetbridge.net | 162.255.165.0/24 |
WHOIS of the domain usb-drivers.org
Domain Name: usb-drivers.org Registry Domain ID: REDACTED Registrar WHOIS Server: http://whois.namesilo.com Registrar URL: http://www.namesilo.com Updated Date: 2026-08-12T03:12:50Z Creation Date: 2013-07-07T08:31:25Z Registry Expiry Date: 2027-07-07T08:31:25Z Registrar: NameSilo, LLC Registrar IANA ID: 1479 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.4805240066 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: ns2.inetbridge.net Name Server: ns1.inetbridge.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-02T22:57:52Z <<< For more information on Whois status codes, please visit https://icann.org/epp Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Domain Name: usb-drivers.org Registry Domain ID: 672e93eb03174ba0b4fc81c76d451fe2-LROR Registrar WHOIS Server: whois.namesilo.com Registrar URL: https://www.namesilo.com/ Updated Date: 2026-09-23T07:00:00Z Creation Date: 2013-07-07T07:00:00Z Registrar Registration Expiration Date: 2027-07-07T07:00:00Z Registrar: NameSilo, LLC Registrar IANA ID: 1479 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +1.4805240066 Domain Status: client transfer prohibited https://www.icann.org/epp#client transfer prohibited Registrant Name: Andre Hector Registrant Organization: Registrant Street: 279/177 Condo C, Lad Proa 121 Bangkok Registrant City: Bangkok Registrant State/Province: Ban Registrant Postal Code: 10012 Registrant Country: TH Registrant Phone: +66.865104922 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: [email protected] Admin Name: Andre Hector Admin Organization: Admin Street: 279/177 Condo C, Lad Proa 121 Bangkok Admin City: Bangkok Admin State/Province: Ban Admin Postal Code: 10012 Admin Country: TH Admin Phone: +66.865104922 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: [email protected] Tech Name: Andre Hector Tech Organization: Tech Street: 279/177 Condo C, Lad Proa 121 Bangkok Tech City: Bangkok Tech State/Province: Ban Tech Postal Code: 10012 Tech Country: TH Tech Phone: +66.865104922 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: [email protected] Name Server: NS1.INETBRIDGE.NET Name Server: NS2.INETBRIDGE.NET DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-10-02T07:00:00Z <<< For more information on Whois status codes, please visit https://icann.org/epp NOTICE AND TERMS OF USE: You are not authorized to access or query our WHOIS database through the use of high-volume, automated, electronic processes. The Data in our WHOIS database is provided for information purposes only, and to assist persons in obtaining information about or related to a domain name registration record. We do not guarantee its accuracy. By submitting a WHOIS query, you agree to abide by the following terms of use: You agree that you may use this Data only for lawful purposes and that under no circumstances will you use this Data to: (1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial advertising or solicitations via e-mail, telephone, or facsimile; or (2) enable high volume, automated, electronic processes that apply to us (or our computer systems). The compilation, repackaging, dissemination or other use of this Data is expressly prohibited without our prior written consent. We reserve the right to terminate your access to the WHOIS database at our sole discretion, including without limitation, for excessive querying of the WHOIS database or for failure to otherwise abide by this policy. We reserve the right to modify these terms at any time. % Query time: 1088 msec % WHEN: Fri Oct 02 22:57:52 UTC 2026