my-subs.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 35 days left6 years oldTranco #135404
40
my-subs.co was registered on 3 Nov 2019 via Dynadot Inc and the registry expiry is 3 Nov 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/my-subs.co.
my-subs.co publishes 2 nameservers. DNSSEC is not signed.
my-subs.co has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from YE2 is valid and has 35 days left (TLS 1.3).
Domain · RDAP/WHOIS
my-subs.co was registered on 3 Nov 2019 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.registry.co/co/domain/my-subs.co.
| Registered | since 3 Nov 2019 |
|---|---|
| Created | 3 November 2019 |
| Updated | 27 October 2026 |
| Expires | 3 November 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | adam.ns.cloudflare.com, sharon.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.registry.co/co/domain/my-subs.co |
my-subs.co 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 adam.ns.cloudflare.com is published for my-subs.co in the registration record from https://rdap.registry.co/co/domain/my-subs.co.
Nameserver sharon.ns.cloudflare.com is published for my-subs.co in the registration record from https://rdap.registry.co/co/domain/my-subs.co.
DNS
my-subs.co has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | adam.ns.cloudflare.com, sharon.ns.cloudflare.com |
| MX | mx.zoho.com (10) Zoho, mx2.zoho.com (20) Zoho, mx3.zoho.com (50) Zoho |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at my-subs.co is "v=spf1 include:zohomail.com include:_spf.mx.cloudflare.net ~all".
IPv4 address 188.114.96.3 answers for my-subs.co at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for my-subs.co at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for my-subs.co at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for my-subs.co at resolver 1.1.1.1:53.
Mail exchanger mx.zoho.com has preference 10. The host is recognised as Zoho.
Mail exchanger mx2.zoho.com has preference 20. The host is recognised as Zoho.
Mail exchanger mx3.zoho.com has preference 50. The host is recognised as Zoho.
Hosting and geo
my-subs.co is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for my-subs.co is valid, with 35 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE2 |
|---|---|
| Subject | my-subs.co |
| Valid from | 7 September 2026 |
| Valid until | 6 December 2026 |
| Days left | 35 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: maintenance.my-subs.co, my-subs.co.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for my-subs.co is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for my-subs.co. That resolver covers adult and malware names.
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 5 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 0 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: rdap created changed from empty to 2019-11-03T20:31:28.0Z.
- October 2026: rdap dnssec changed from unknown to no.
- October 2026: rdap expires changed from empty to 2027-11-03T23:59:59.0Z.
- October 2026: rdap nameservers changed from empty to adam.ns.cloudflare.com,sharon.ns.cloudflare.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to Dynadot Inc.
- October 2026: rdap statuses changed from empty to client transfer prohibited.
- October 2026: rdap updated changed from empty to 2026-10-27T15:52:05.0Z.
Questions
Is my-subs.co safe?
Cloudflare family DNS returned a block for my-subs.co. That resolver covers adult and malware names.
Who hosts my-subs.co?
my-subs.co is placed in Toronto, Canada.
When does my-subs.co expire?
my-subs.co expires on 3 November 2027 according to https://rdap.registry.co/co/domain/my-subs.co.
Who owns my-subs.co?
The registry did not return a person or a company for my-subs.co. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.registry.co/co/domain/my-subs.co at 2026-10-30T13:39:27Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:39:27Z
- TLS source tls:443 at 2026-10-30T13:39:27Z
- HTTP source https://my-subs.co/ at 2026-10-30T13:39:27Z
- Tech source not available at 2026-10-30T13:39:27Z
- Geo source db-ip at 2026-10-30T13:39:27Z
- Safety source family DNS and local lists at 2026-10-30T13:39: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.