qafone.co
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
70
qafone.co was registered on 12 Mar 2011 via GoDaddy.com, LLC and the registry expiry is 11 Mar 2027. WHOIS data came from RDAP at https://rdap.registry.co/co/domain/qafone.co.
qafone.co publishes 2 nameservers. DNSSEC is not signed.
qafone.co has 2 IPv4 addresses (15.197.148.33, 3.33.130.190). The geolocation database places 15.197.148.33 in Montreal, Canada.
The TLS certificate from GoDaddy TLS Intermediate CA DV - R1v1 is valid and has 88 days left (TLS 1.3). The homepage answered HTTP 200.
No safety warning was recorded for qafone.co in the checks that ran.
qafone.co was registered on 12 Mar 2011 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://rdap.registry.co/co/domain/qafone.co.
| Registered | since 12 Mar 2011 |
|---|---|
| Created | 12 March 2011 |
| Updated | 14 July 2026 |
| Expires | 11 March 2027 |
| Registrar | GoDaddy.com, LLC |
| Status | client renew prohibited, client transfer prohibited, client update prohibited, client delete prohibited |
| Nameservers | ns27.domaincontrol.com, ns28.domaincontrol.com |
| DNSSEC | no |
| Source | https://rdap.registry.co/co/domain/qafone.co |
qafone.co 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.
qafone.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.
qafone.co 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.
qafone.co 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.
Nameserver ns27.domaincontrol.com is published for qafone.co in the registration record from https://rdap.registry.co/co/domain/qafone.co.
Nameserver ns28.domaincontrol.com is published for qafone.co in the registration record from https://rdap.registry.co/co/domain/qafone.co.
qafone.co has 2 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 15.197.148.33, 3.33.130.190 |
|---|---|
| AAAA | — |
| NS | ns27.domaincontrol.com, ns28.domaincontrol.com |
| MX | — |
| SPF | absent |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The DMARC text record at _dmarc.qafone.co is "v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:[email protected];".
IPv4 address 15.197.148.33 answers for qafone.co at resolver 1.1.1.1:53.
IPv4 address 3.33.130.190 answers for qafone.co at resolver 1.1.1.1:53.
qafone.co is placed in Montreal, Canada by the local geolocation database (db-ip).
| Address | 15.197.148.33 |
|---|---|
| Country | Canada |
| City | Montreal |
| Source | db-ip |
The certificate for qafone.co is valid, with 88 days left and 1 subject alternative name. Source: tls:443.
| Issuer | GoDaddy TLS Intermediate CA DV - R1v1 |
|---|---|
| Subject | qafone.co |
| Valid from | 14 July 2026 |
| Valid until | 28 January 2027 |
| Days left | 88 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: qafone.co.
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
The homepage returned HTTP 200 in 126 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 126 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| 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 qafone.co 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 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 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.
qafone.co is placed in Montreal, Canada.
qafone.co expires on 11 March 2027 according to https://rdap.registry.co/co/domain/qafone.co.
The registry did not return a person or a company for qafone.co. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
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.