propatientco.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
60
propatientco.com was registered on 17 Nov 2011 via CSC Corporate Domains, Inc. and the registry expiry is 17 Nov 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/propatientco.com.
propatientco.com publishes 2 nameservers. DNSSEC is not signed.
propatientco.com has 4 IPv4 addresses (18.239.105.109, 18.239.105.111, 18.239.105.49, 18.239.105.58). The geolocation database places 18.239.105.109 in Amsterdam, The Netherlands.
The TLS certificate from Amazon RSA 2048 M01 is valid and has 82 days left (TLS 1.3).
Tech detection named Amazon CloudFront and Amazon Web Services. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for propatientco.com in the checks that ran.
propatientco.com was registered on 17 Nov 2011 via CSC Corporate Domains, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/propatientco.com.
| Registered | since 17 Nov 2011 |
|---|---|
| Created | 17 November 2011 |
| Updated | 24 September 2026 |
| Expires | 17 November 2027 |
| Registrar | CSC Corporate Domains, Inc. |
| Status | client transfer prohibited |
| Nameservers | jessica.ns.cloudflare.com, micah.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/propatientco.com |
propatientco.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.
Nameserver jessica.ns.cloudflare.com is published for propatientco.com in the registration record from https://rdap.verisign.com/com/v1/domain/propatientco.com.
Nameserver micah.ns.cloudflare.com is published for propatientco.com in the registration record from https://rdap.verisign.com/com/v1/domain/propatientco.com.
propatientco.com has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 18.239.105.109, 18.239.105.111, 18.239.105.49, 18.239.105.58 |
|---|---|
| AAAA | — |
| NS | jessica.ns.cloudflare.com, micah.ns.cloudflare.com |
| MX | — |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at propatientco.com is "v=spf1 -all".
The DMARC text record at _dmarc.propatientco.com is "v=DMARC1; p=reject; rua=mailto:[email protected]".
IPv4 address 18.239.105.109 answers for propatientco.com at resolver 1.1.1.1:53.
IPv4 address 18.239.105.111 answers for propatientco.com at resolver 1.1.1.1:53.
IPv4 address 18.239.105.49 answers for propatientco.com at resolver 1.1.1.1:53.
IPv4 address 18.239.105.58 answers for propatientco.com at resolver 1.1.1.1:53.
propatientco.com is placed in Amsterdam, The Netherlands by the local geolocation database (db-ip).
| Address | 18.239.105.109 |
|---|---|
| Country | The Netherlands |
| City | Amsterdam |
| Source | db-ip |
The certificate for propatientco.com is valid, with 82 days left and 4 subject alternative names. Source: tls:443.
| Issuer | Amazon RSA 2048 M01 |
|---|---|
| Subject | propatientco.patientco.engineering |
| Valid from | 8 July 2026 |
| Valid until | 21 January 2027 |
| Days left | 82 |
| SAN count | 4 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: propatientco.com, propatientco.patientco.engineering, www.propatientco.com, www.propatientco.patientco.engineering.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Amazon CloudFront is filed under CDN.
Amazon Web Services is filed under PaaS.
The homepage returned HTTP 403 in 5 ms. The target title is 41 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 5 ms |
| Title length | 41 yes |
| Quoted title | "ERROR: The request could not be satisfied" |
| 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.
Family DNS for propatientco.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.
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.
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
propatientco.com is placed in Amsterdam, The Netherlands.
propatientco.com expires on 17 November 2027 according to https://rdap.verisign.com/com/v1/domain/propatientco.com.
The registry did not return a person or a company for propatientco.com. RDAP often redacts the registrant. The registrar on file is CSC Corporate Domains, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.