Summary
- Registrar
- Nom-iq Ltd. dba COM LAUDE
- Status
- clientDeleteProhibited
- Created on
- April 7, 2000
- Expires on
- April 7, 2027
- Name servers
- dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p02.nsone.net, dns2.p02.nsone.net, dns1.p01.nsone.net, dns2.p01.nsone.net
- Mail servers
- mx1.redhat.com, mx2.redhat.com
- DMARC
- Monitoring
- SPF
- Incomplete
- DKIM
- No key found among the common selectors
- Website
- See the website
Spoofing protection (DMARC)
E-mails spoofing this domain are only reported, not blocked.
DMARC tells mail servers what to do with an e-mail that claims to come from jboss.org but fails SPF and DKIM checks.
- Policy
- Monitoring
- Subdomain policy
- Monitoring
- Messages covered
- 100%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- [email protected]
- Failure reports
- —
Record
v=DMARC1; p=none; rua=mailto:[email protected]; sp=none; ri=86400
Authorized senders (SPF)
The record does not end with an "all" rule: other servers are not explicitly rejected.
SPF lists the servers allowed to send e-mails for jboss.org.
| Rule | Value | Result |
|---|---|---|
| include | redhat.com | Allowed |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 include:redhat.com
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 jboss.org arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from jboss.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 @jboss.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
jboss.org MX 10 mx1.jboss.org. jboss.org MX 20 mx2.jboss.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.jboss.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
jboss.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.jboss.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.jboss.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.jboss.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.jboss.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 jboss.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 | 18.185.24.46 |
| A | 3.71.139.153 |
| A | 3.126.5.188 |
| AAAA | 2a05:d014:803:f30c:505c:9738:13c:b7a5 |
| AAAA | 2a05:d014:803:f30a:4c8d:5530:dac2:179 |
| AAAA | 2a05:d014:803:f30e:ffe5:90d1:736a:fcad |
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 |
|---|---|
| dns3.p01.nsone.net | 198.51.44.65 |
| dns4.p01.nsone.net | 198.51.45.65 |
| dns1.p02.nsone.net | 198.51.44.2 |
| dns2.p02.nsone.net | 198.51.45.2 |
| dns1.p01.nsone.net | 198.51.44.1 |
| dns2.p01.nsone.net | 198.51.45.1 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @jboss.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 |
|---|---|---|
| 10 | mx1.redhat.com | 52.25.184.255 |
| 20 | mx2.redhat.com | 52.25.184.255 |
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.jboss.org.
| Name | Content |
|---|---|
| jboss.org | _mt54jlqxkfymlsvw7327uacswerj3s8 |
| jboss.org | v=spf1 include:redhat.com |
| _dmarc.jboss.org | v=DMARC1; p=none; rua=mailto:[email protected]; sp=none; ri=86400 |
Related IP addresses
IPv4 addresses used by jboss.org: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 18.185.24.46 | Website | 18.185.24.0/24 |
| 3.71.139.153 | Website | 3.71.139.0/24 |
| 3.126.5.188 | Website | 3.126.5.0/24 |
| 198.51.44.65 | Name server dns3.p01.nsone.net | 198.51.44.0/24 |
| 198.51.45.65 | Name server dns4.p01.nsone.net | 198.51.45.0/24 |
| 198.51.44.2 | Name server dns1.p02.nsone.net | 198.51.44.0/24 |
| 198.51.45.2 | Name server dns2.p02.nsone.net | 198.51.45.0/24 |
| 198.51.44.1 | Name server dns1.p01.nsone.net | 198.51.44.0/24 |
| 198.51.45.1 | Name server dns2.p01.nsone.net | 198.51.45.0/24 |
| 52.25.184.255 | Mail server mx1.redhat.com, Mail server mx2.redhat.com | 52.25.184.0/24 |
WHOIS of the domain jboss.org
Domain Name: jboss.org Registry Domain ID: REDACTED Registrar WHOIS Server: whois.comlaude.com Registrar URL: https://comlaude.com/whois Updated Date: 2026-08-12T04:40:05Z Creation Date: 2000-04-07T19:13:52Z Registry Expiry Date: 2027-04-07T19:13:51Z Registrar: Nom-iq Ltd. dba COM LAUDE Registrar IANA ID: 470 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +44.2074218250 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Name Server: dns1.p01.nsone.net Name Server: dns1.p02.nsone.net Name Server: dns2.p01.nsone.net Name Server: dns2.p02.nsone.net Name Server: dns3.p01.nsone.net Name Server: dns4.p01.nsone.net DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-02T19:42:20Z <<< 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: jboss.org Registry Domain ID: Registrar WHOIS Server: whois.comlaude.com Registrar URL: https://www.comlaude.com Updated Date: 2026-08-12T04:40:05Z Creation Date: 2000-04-07T00:00:00Z Registrar Registration Expiration Date: 2027-04-07T00:00:00Z Registrar: NOM-IQ Ltd dba Com Laude Registrar IANA ID: 470 Domain Status: clientDeleteProhibited https://www.icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://www.icann.org/epp#clientUpdateProhibited Registry Registrant ID: REDACTED Registrant Name: REDACTED Registrant Organization: Red Hat, Inc. Registrant Street: REDACTED Registrant City: REDACTED Registrant State/Province: North Carolina Registrant Postal Code: REDACTED Registrant Country: US Registrant Phone: REDACTED Registrant Phone Ext: REDACTED Registrant Fax: REDACTED Registrant Fax Ext: REDACTED Registrant Email: [email protected] Registry Admin ID: REDACTED Admin Name: REDACTED Admin Organization: REDACTED Admin Street: REDACTED Admin City: REDACTED Admin State/Province: REDACTED Admin Postal Code: REDACTED Admin Country: REDACTED Admin Phone: REDACTED Admin Phone Ext: REDACTED Admin Fax: REDACTED Admin Fax Ext: REDACTED Admin Email: [email protected] Registry Tech ID: REDACTED Tech Name: REDACTED Tech Organization: REDACTED Tech Street: REDACTED Tech City: REDACTED Tech State/Province: REDACTED Tech Postal Code: REDACTED Tech Country: REDACTED Tech Phone: REDACTED Tech Phone Ext: REDACTED Tech Fax: REDACTED Tech Fax Ext: REDACTED Tech Email: [email protected] Name Server: dns1.p01.nsone.net Name Server: dns2.p01.nsone.net Name Server: dns3.p01.nsone.net Name Server: dns4.p01.nsone.net Name Server: dns1.p02.nsone.net Name Server: dns2.p02.nsone.net DNSSEC: Unsigned Delegation Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +44.2074218250 URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-10-02T19:42:20Z <<< For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. ------------------------------------------------------------------------------- Com Laude registers, maintains and renews domain names around the world for leading intellectual property owners and the law firms that support them. If you have queries about this domain, you may contact us via our website at www.comlaude.com. ------------------------------------------------------------------------------- The data in the Com Laude Whois database is provided to assist you in obtaining information about a domain name registration record. Com Laude makes this information available "as is," and does not guarantee its accuracy. By submitting a WHOIS query, you agree that you will 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 (spam), telephone or fax; or (2) enable high volume, automated, electronic processes that that send queries or data to Com Laude or the systems of any Registry Operator or ICANN-Accredited registrar. The compilation, repackaging, dissemination or other use of this data is expressly prohibited without the prior written consent of Com Laude. Com Laude reserves the right to modify these terms at any time. By submitting this query, you agree to abide by these terms. If you fail to abide by this policy, we may terminate your access to this WHOIS database. ------------------------------------------------------------------------------- Com Laude protects intellectual property in the domain name system. Com Laude only registers domain names for legitimate rights owners. Should you have any queries about the legitimacy of this name or our work as a UK based, ICANN Accredited Registrar, contact us at: Com Laude, 28 Little Russell Street, London WC1A 2HN, UK. Com Laude is a business name of Nom IQ Ltd. ------------------------------------------------------------------------------- % Query time: 891 msec % WHEN: Fri Oct 02 19:42:19 UTC 2026