cftpay.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 401SafeSSL: 36 days left16 years oldTranco #308723
65
cftpay.com was registered on 5 Apr 2010 via GoDaddy.com, LLC and the registry expiry is 5 Apr 2028. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/cftpay.com.
cftpay.com publishes 4 nameservers. DNSSEC is not signed.
cftpay.com has 2 IPv4 addresses (34.236.236.181, 54.227.144.52). The geolocation database places 34.236.236.181 in Ashburn, United States.
The TLS certificate from Sectigo Public Server Authentication CA DV R36 is valid and has 36 days left (TLS 1.2).
Tech detection named Cloudflare and Cloudflare Bot Management. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for cftpay.com in the checks that ran.
Domain · RDAP/WHOIS
cftpay.com was registered on 5 Apr 2010 via GoDaddy.com, LLC. The registry returned 4 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/cftpay.com.
| Registered | since 5 Apr 2010 |
|---|---|
| Created | 5 April 2010 |
| Updated | 29 September 2024 |
| Expires | 5 April 2028 |
| Registrar | GoDaddy.com, LLC |
| Status | client delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited |
| Nameservers | ns-1288.awsdns-33.org, ns-144.awsdns-18.com, ns-1557.awsdns-02.co.uk, ns-680.awsdns-21.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/cftpay.com |
cftpay.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.
cftpay.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.
cftpay.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.
cftpay.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-1288.awsdns-33.org is published for cftpay.com in the registration record from https://rdap.verisign.com/com/v1/domain/cftpay.com.
Nameserver ns-144.awsdns-18.com is published for cftpay.com in the registration record from https://rdap.verisign.com/com/v1/domain/cftpay.com.
Nameserver ns-1557.awsdns-02.co.uk is published for cftpay.com in the registration record from https://rdap.verisign.com/com/v1/domain/cftpay.com.
Nameserver ns-680.awsdns-21.net is published for cftpay.com in the registration record from https://rdap.verisign.com/com/v1/domain/cftpay.com.
DNS
cftpay.com has 2 address records, 6 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 34.236.236.181, 54.227.144.52 |
|---|---|
| AAAA | — |
| NS | ns-1288.awsdns-33.org, ns-144.awsdns-18.com, ns-1557.awsdns-02.co.uk, ns-680.awsdns-21.net |
| MX | aspmx.l.google.com (10) Google, alt1.aspmx.l.google.com (20) Google, alt2.aspmx.l.google.com (30) Google, aspmx2.googlemail.com (40) Google, aspmx3.googlemail.com (50) Google, inbound-smtp.us-east-1.amazonaws.com (60) |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at cftpay.com is "v=spf1 include:_spf.google.com ~all".
The DMARC text record at _dmarc.cftpay.com is "v=DMARC1; p=none; rua=mailto:[email protected]".
IPv4 address 34.236.236.181 answers for cftpay.com at resolver 1.1.1.1:53.
IPv4 address 54.227.144.52 answers for cftpay.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 20. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 30. The host is recognised as Google.
Mail exchanger aspmx2.googlemail.com has preference 40. The host is recognised as Google.
Mail exchanger aspmx3.googlemail.com has preference 50. The host is recognised as Google.
Mail exchanger inbound-smtp.us-east-1.amazonaws.com has preference 60.
Hosting and geo
cftpay.com is placed in Ashburn, United States by the local geolocation database (db-ip).
| Address | 34.236.236.181 |
|---|---|
| Country | United States |
| City | Ashburn |
| Source | db-ip |
SSL/TLS
The certificate for cftpay.com is valid, with 36 days left and 2 subject alternative names. Source: tls:443.
| Issuer | Sectigo Public Server Authentication CA DV R36 |
|---|---|
| Subject | *.cftpay.com |
| Valid from | 22 May 2026 |
| Valid until | 6 December 2026 |
| Days left | 36 |
| SAN count | 2 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Subject alternative names: *.cftpay.com, cftpay.com.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- Cloudflare Bot Management · Security
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
On-page checks
The homepage returned HTTP 401 in 93 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 401 |
|---|---|
| TTFB | 93 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| 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 cftpay.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 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 Ashburn.
- October 2026: geo country changed from empty to United States.
Questions
Is cftpay.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 cftpay.com?
cftpay.com is placed in Ashburn, United States.
When does cftpay.com expire?
cftpay.com expires on 5 April 2028 according to https://rdap.verisign.com/com/v1/domain/cftpay.com.
Who owns cftpay.com?
The registry did not return a person or a company for cftpay.com. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/cftpay.com at 2026-10-30T13:49:15Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:49:15Z
- TLS source tls:443 at 2026-10-30T13:49:15Z
- HTTP source https://cftpay.com/ at 2026-10-30T13:49:15Z
- Tech source wappalyzergo at 2026-10-30T13:49:15Z
- Geo source db-ip at 2026-10-30T13:49:15Z
- Safety source family DNS and local lists at 2026-10-30T13:49:15Z
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.