fiercehealthcare.com
fiercehealthcare.com is registered with Nom-iq Ltd. dba COM LAUDE since February 25, 2004 (22.7 years). The registration expires on February 25, 2027. Its email security grade is F. Its SSL certificate is issued by Google Trust Services and is valid for 36 more days.
- Domain age
- 22.7 yrs
- Technologies
- —
- Email security
- F
- SSL days left
- 36
Registration
| Registrar | Nom-iq Ltd. dba COM LAUDE |
|---|---|
| IANA ID | 470 |
| Registered | February 25, 2004 |
| Expires | February 25, 2027 |
| Updated | January 26, 2026 |
| Status | client delete prohibited, client transfer prohibited, client update prohibited |
| Name servers | hans.ns.cloudflare.com, melissa.ns.cloudflare.com |
| DNSSEC | Not signed |
DNS records
| Type | Value | TTL |
|---|---|---|
| A | 104.17.130.109 | 300 |
| A | 104.17.131.109 | 300 |
| MX | mx1.emailsrvr.com 10 | 120 |
| MX | mx2.emailsrvr.com 20 | 120 |
| NS | hans.ns.cloudflare.com | 86400 |
| NS | melissa.ns.cloudflare.com | 86400 |
| CAA | issue 0 comodoca.com | 3600 |
| CAA | issue 0 digicert.com; cansignhttpexchanges=yes | 3600 |
| CAA | issue 0 letsencrypt.org | 3600 |
| CAA | issue 0 pki.goog; cansignhttpexchanges=yes | 3600 |
| CAA | issue 0 ssl.com | 3600 |
| CAA | issuewild 0 comodoca.com | 3600 |
| CAA | issuewild 0 digicert.com; cansignhttpexchanges=yes | 3600 |
| CAA | issuewild 0 letsencrypt.org | 3600 |
| CAA | issuewild 0 pki.goog; cansignhttpexchanges=yes | 3600 |
| CAA | issuewild 0 ssl.com | 3600 |
| TXT | facebook-domain-verification=e1r6npgbhjurf6xgil4y2ggu73iimx | 300 |
| TXT | google-site-verification=M31trxYsGV2a12WRflyCXyDY6SDfY6hX3jWQvd0Q2Xw | 300 |
| TXT | google-site-verification=co_ejdiwm37KXNV9o55sJS4NjYqXcQR-8uAiPiIOwww | 300 |
| TXT | v=spf1 include:mktomail.com -all include:emailsrvr.com -all | 300 |
SSL certificate
| Valid | Valid |
|---|---|
| Issuer | US, WE1, Google Trust Services |
| Expires | December 16, 2026 |
| Days remaining | 36 |
| Protocol | TLSv1.3 |
| Names | fiercehealthcare.com, *.fiercehealthcare.com |
Email security
- badNo DMARC record. Receivers have no instructions for mail that fails SPF and DKIM, and you get no reports about who sends as your domain.
- 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.
- goodSPF ends with -all: servers you have not listed are rejected (hard fail).
- good2 MX record(s) found. Mail is handled by Rackspace.
About fiercehealthcare.com
Who is the registrar of fiercehealthcare.com?
fiercehealthcare.com is registered with Nom-iq Ltd. dba COM LAUDE (IANA ID 470).
When does fiercehealthcare.com expire?
The current registration of fiercehealthcare.com expires on February 25, 2027. It was first registered on February 25, 2004.
Does fiercehealthcare.com protect its email with SPF and DMARC?
fiercehealthcare.com scores 30/100 (grade F) for email security. No DMARC record. Receivers have no instructions for mail that fails SPF and DKIM, and you get no reports about who sends as your domain. No DKIM key found at common selectors (google, selector1, selector2, default, k1, k2, s1, s2, ...). DKIM may still use a custom selector we cannot guess.
What are the name servers of fiercehealthcare.com?
fiercehealthcare.com uses hans.ns.cloudflare.com, melissa.ns.cloudflare.com.