cooperfamilyoffice.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 22 days left10 years old
75
cooperfamilyoffice.com was registered on 3 Sep 2016 via 1API GmbH and the registry expiry is 3 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com.
cooperfamilyoffice.com publishes 2 nameservers. DNSSEC is not signed.
cooperfamilyoffice.com has 3 IPv4 addresses (185.230.63.107, 185.230.63.171, 185.230.63.186). The geolocation database places 185.230.63.107 in Washington D.C., United States.
The TLS certificate from WR1 is valid and has 22 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Cloudflare, Cloudflare Bot Management, HSTS, HTTP/3, Lodash, React and Wix. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for cooperfamilyoffice.com in the checks that ran.
Domain · RDAP/WHOIS
cooperfamilyoffice.com was registered on 3 Sep 2016 via 1API GmbH. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com.
| Registered | since 3 Sep 2016 |
|---|---|
| Created | 3 September 2016 |
| Updated | 3 September 2026 |
| Expires | 3 September 2027 |
| Registrar | 1API GmbH |
| Status | client transfer prohibited |
| Nameservers | ns0.wixdns.net, ns1.wixdns.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com |
cooperfamilyoffice.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 ns0.wixdns.net is published for cooperfamilyoffice.com in the registration record from https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com.
Nameserver ns1.wixdns.net is published for cooperfamilyoffice.com in the registration record from https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com.
DNS
cooperfamilyoffice.com has 3 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 185.230.63.107, 185.230.63.171, 185.230.63.186 |
|---|---|
| AAAA | — |
| NS | ns0.wixdns.net, ns1.wixdns.net |
| MX | cooperfamilyoffice-com.mail.protection.outlook.com (10) Microsoft 365 |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at cooperfamilyoffice.com is "v=spf1 include:spf.protection.outlook.com -all".
IPv4 address 185.230.63.107 answers for cooperfamilyoffice.com at resolver 1.1.1.1:53.
IPv4 address 185.230.63.171 answers for cooperfamilyoffice.com at resolver 1.1.1.1:53.
IPv4 address 185.230.63.186 answers for cooperfamilyoffice.com at resolver 1.1.1.1:53.
Mail exchanger cooperfamilyoffice-com.mail.protection.outlook.com has preference 10. The host is recognised as Microsoft 365.
Hosting and geo
cooperfamilyoffice.com is placed in Washington D.C., United States by the local geolocation database (db-ip).
| Address | 185.230.63.107 |
|---|---|
| Country | United States |
| City | Washington D.C. |
| Source | db-ip |
SSL/TLS
The certificate for cooperfamilyoffice.com is valid, with 22 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WR1 |
|---|---|
| Subject | cooperfamilyoffice.com |
| Valid from | 25 August 2026 |
| Valid until | 23 November 2026 |
| Days left | 22 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: cooperfamilyoffice.com, www.cooperfamilyoffice.com.
Tech stack
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- HSTS · Security
- HTTP/3 · Miscellaneous
- Lodash · JavaScript libraries
- React · JavaScript frameworks
- Wix · CMS, Blogs
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Lodash is filed under JavaScript libraries.
React is filed under JavaScript frameworks.
Wix is filed under CMS, Blogs.
On-page checks
The homepage returned HTTP 200 in 103 ms. The target title is 27 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 103 ms |
| Title length | 27 yes |
| Quoted title | "Home | Cooper Family Office" |
| Meta description | none no |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://www.cooperfamilyoffice.com |
| Language | en |
| Links | 59 |
| Images | 2 |
| Favicon | yes |
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 cooperfamilyoffice.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 | yes |
| 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 25 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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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 Washington D.C..
- October 2026: geo country changed from empty to United States.
Questions
Is cooperfamilyoffice.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 cooperfamilyoffice.com?
cooperfamilyoffice.com is placed in Washington D.C., United States.
When does cooperfamilyoffice.com expire?
cooperfamilyoffice.com expires on 3 September 2027 according to https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com.
Who owns cooperfamilyoffice.com?
The registry did not return a person or a company for cooperfamilyoffice.com. RDAP often redacts the registrant. The registrar on file is 1API GmbH.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/cooperfamilyoffice.com at 2026-10-30T13:50:27Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:50:27Z
- TLS source tls:443 at 2026-10-30T13:50:27Z
- HTTP source https://cooperfamilyoffice.com/ at 2026-10-30T13:50:27Z
- Tech source wappalyzergo at 2026-10-30T13:50:27Z
- Geo source db-ip at 2026-10-30T13:50:27Z
- Safety source family DNS and local lists at 2026-10-30T13:50:27Z
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.