ehealthdeck.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 109 days left10 years old
60
ehealthdeck.com was registered on 1 Sep 2016 via GoDaddy.com, LLC and the registry expiry is 1 Sep 2036. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
ehealthdeck.com publishes 4 nameservers. DNSSEC is not signed.
ehealthdeck.com has 3 IPv4 addresses (18.208.78.163, 34.203.19.243, 35.174.93.120). The geolocation database places 18.208.78.163 in Ashburn, United States.
The TLS certificate from Amazon RSA 2048 M01 is valid and has 109 days left (TLS 1.3).
Tech detection named Amazon ELB and Amazon Web Services. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for ehealthdeck.com in the checks that ran.
Domain · RDAP/WHOIS
ehealthdeck.com was registered on 1 Sep 2016 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
| Registered | since 1 Sep 2016 |
|---|---|
| Created | 1 September 2016 |
| Updated | 2 September 2026 |
| Expires | 1 September 2036 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1363.awsdns-42.org, ns-1963.awsdns-53.co.uk, ns-285.awsdns-35.com, ns-868.awsdns-44.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/ehealthdeck.com |
ehealthdeck.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
ehealthdeck.com carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.
ehealthdeck.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
ehealthdeck.com carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver ns-1363.awsdns-42.org is published for ehealthdeck.com in the registration record from https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
Nameserver ns-1963.awsdns-53.co.uk is published for ehealthdeck.com in the registration record from https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
Nameserver ns-285.awsdns-35.com is published for ehealthdeck.com in the registration record from https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
Nameserver ns-868.awsdns-44.net is published for ehealthdeck.com in the registration record from https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
DNS
ehealthdeck.com has 3 address records, 1 mail exchanger and 4 nameservers, measured at 1.1.1.1:53.
| A | 18.208.78.163, 34.203.19.243, 35.174.93.120 |
|---|---|
| AAAA | — |
| NS | ns-1363.awsdns-42.org, ns-1963.awsdns-53.co.uk, ns-285.awsdns-35.com, ns-868.awsdns-44.net |
| MX | ehealthdeck-com.mail.protection.outlook.com (0) Microsoft 365 |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at ehealthdeck.com is "v=spf1 include:spf.protection.outlook.com -all".
The DMARC text record at _dmarc.ehealthdeck.com is "v=DMARC1; p=reject; sp=reject; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1".
IPv4 address 18.208.78.163 answers for ehealthdeck.com at resolver 1.1.1.1:53.
IPv4 address 34.203.19.243 answers for ehealthdeck.com at resolver 1.1.1.1:53.
IPv4 address 35.174.93.120 answers for ehealthdeck.com at resolver 1.1.1.1:53.
Mail exchanger ehealthdeck-com.mail.protection.outlook.com has preference 0. The host is recognised as Microsoft 365.
Hosting and geo
ehealthdeck.com is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 18.208.78.163 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for ehealthdeck.com is valid, with 109 days left and 1 subject alternative name. Source: tls:443.
| Issuer | Amazon RSA 2048 M01 |
|---|---|
| Subject | ehealthdeck.com |
| Valid from | 20 January 2026 |
| Valid until | 17 February 2027 |
| Days left | 109 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: ehealthdeck.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Amazon ELB · Load balancers
- Amazon Web Services · PaaS
Amazon ELB is filed under Load balancers.
Amazon Web Services is filed under PaaS.
On-page checks
The homepage returned HTTP 403 in 98 ms. The target title is 13 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 98 ms |
| Title length | 13 yes |
| Quoted title | "403 Forbidden" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for ehealthdeck.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 10 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is ehealthdeck.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts ehealthdeck.com?
ehealthdeck.com is placed in Ashburn, United States.
When does ehealthdeck.com expire?
ehealthdeck.com expires on 1 September 2036 according to https://rdap.verisign.com/com/v1/domain/ehealthdeck.com.
Who owns ehealthdeck.com?
The registry did not return a person or a company for ehealthdeck.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/ehealthdeck.com at 2026-10-30T13:52:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:52:49Z
- TLS source tls:443 at 2026-10-30T13:52:49Z
- HTTP source https://ehealthdeck.com/ at 2026-10-30T13:52:49Z
- Tech source wappalyzergo at 2026-10-30T13:52:49Z
- Geo source db-ip at 2026-10-30T13:52:49Z
- Safety source family DNS and local lists at 2026-10-30T13:52:49Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.