jboss.org
This Week in JBoss - July 03, 2023 - JBoss.org
jboss.org is registered with Nom-iq Ltd. dba COM LAUDE since April 8, 2000 (26.6 years). The registration expires on April 8, 2027. The site runs on Hotjar, cdnjs, TrustArc and 5 other technologies. Its email security grade is F. Its SSL certificate is issued by Let's Encrypt and is valid for 48 more days.
- Domain age
- 26.6 yrs
- Technologies
- 8
- Email security
- F
- SSL days left
- 48
Registration
| Registrar | Nom-iq Ltd. dba COM LAUDE |
|---|---|
| IANA ID | 470 |
| Registered | April 8, 2000 |
| Expires | April 8, 2027 |
| Updated | August 12, 2026 |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Name servers | dns1.p01.nsone.net, dns1.p02.nsone.net, dns2.p01.nsone.net, dns2.p02.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net |
| DNSSEC | Not signed |
DNS records
| Type | Value | TTL |
|---|---|---|
| A | 3.126.5.188 | 3600 |
| A | 18.185.24.46 | 3600 |
| A | 3.71.139.153 | 3600 |
| MX | mx1.redhat.com 10 | 3600 |
| MX | mx2.redhat.com 20 | 3600 |
| NS | dns1.p01.nsone.net | 3600 |
| NS | dns2.p01.nsone.net | 3600 |
| NS | dns3.p01.nsone.net | 3600 |
| NS | dns4.p01.nsone.net | 3600 |
| NS | dns1.p02.nsone.net | 3600 |
| NS | dns2.p02.nsone.net | 3600 |
| CAA | issue 0 letsencrypt.org | 3600 |
| CAA | issue 0 digicert.com | 3600 |
| CAA | iodef 0 mailto:[email protected] | 3600 |
| TXT | v=spf1 include:redhat.com | 3600 |
| TXT | _mt54jlqxkfymlsvw7327uacswerj3s8 | 3600 |
| AAAA | 2a05:d014:803:f30e:ffe5:90d1:736a:fcad | 3600 |
| AAAA | 2a05:d014:803:f30c:505c:9738:13c:b7a5 | 3600 |
| AAAA | 2a05:d014:803:f30a:4c8d:5530:dac2:179 | 3600 |
Technology stack
Analytics and advertising IDs
google_tag_manager:GTM-NJWS5LSSL certificate
| Valid | Valid |
|---|---|
| Issuer | US, YE1, Let's Encrypt |
| Expires | December 28, 2026 |
| Days remaining | 48 |
| Protocol | TLSv1.3 |
| Names | jboss.org |
Email security
- warnSPF has no 'all' rule, so mail from unlisted servers gets a neutral result. End it with ~all or -all.
- warnSPF uses 10 of the 10 allowed DNS lookups. Adding another service may break it.
- warnDMARC policy is none (monitoring only). Spoofed mail is still delivered.
- warnNo DKIM key found at common selectors (google, selector1, selector2, default, k1, k2, s1, s2, ...). DKIM may still use a custom selector we cannot guess.
- warnNo MTA-STS: mail sent to you can be downgraded to an unencrypted connection.
- warnNo TLS-RPT record, so you won't hear about failed encrypted deliveries.
- warnNo BIMI record (optional: shows your logo next to your emails in supporting inboxes).
- goodSPF record found.
- goodDMARC aggregate reports are sent to mailto:[email protected].
- good2 MX record(s) found.
Homepage metadata
| Title | This Week in JBoss - July 03, 2023 - JBoss.org |
|---|---|
| Language | en |
| Indexable | Yes |
| Word count | 376 |
About jboss.org
Who is the registrar of jboss.org?
jboss.org is registered with Nom-iq Ltd. dba COM LAUDE (IANA ID 470).
When does jboss.org expire?
The current registration of jboss.org expires on April 8, 2027. It was first registered on April 8, 2000.
What technology does jboss.org use?
We detected 8 technologies on jboss.org, including Hotjar, cdnjs, TrustArc, Font Awesome, Google Fonts, HSTS.
Does jboss.org protect its email with SPF and DMARC?
jboss.org scores 39/100 (grade F) for email security. SPF has no 'all' rule, so mail from unlisted servers gets a neutral result. End it with ~all or -all. SPF uses 10 of the 10 allowed DNS lookups. Adding another service may break it.
What are the name servers of jboss.org?
jboss.org uses dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net, dns1.p02.nsone.net, dns2.p02.nsone.net.