cums.net
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403Family DNS blockedSSL: 83 days left25 years oldTranco #15669
55
cums.net was registered on 11 Mar 2001 via NameCheap, Inc. and the registry expiry is 11 Mar 2028. WHOIS data came from RDAP at https://rdap.verisign.com/net/v1/domain/cums.net.
cums.net publishes 2 nameservers. DNSSEC is not signed.
cums.net has 2 IPv4 addresses (104.20.38.8, 172.66.149.177) and 2 IPv6 addresses (2606:4700:10::6814:2608, 2606:4700:10::ac42:95b1). The geolocation database places 104.20.38.8 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 83 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
Domain · RDAP/WHOIS
cums.net was registered on 11 Mar 2001 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/net/v1/domain/cums.net.
| Registered | since 11 Mar 2001 |
|---|---|
| Created | 11 March 2001 |
| Updated | 20 July 2026 |
| Expires | 11 March 2028 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ns1.cums.net, ns2.cums.net |
| DNSSEC | no |
| Source | https://rdap.verisign.com/net/v1/domain/cums.net |
cums.net 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 ns1.cums.net is published for cums.net in the registration record from https://rdap.verisign.com/net/v1/domain/cums.net.
Nameserver ns2.cums.net is published for cums.net in the registration record from https://rdap.verisign.com/net/v1/domain/cums.net.
DNS
cums.net has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.20.38.8, 172.66.149.177 |
|---|---|
| AAAA | 2606:4700:10::6814:2608, 2606:4700:10::ac42:95b1 |
| NS | ns1.cums.net, ns2.cums.net |
| MX | mx.zoho.eu (10), mx2.zoho.eu (20), mx3.zoho.eu (30) |
| SPF | present |
| DMARC | present |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at cums.net is "v=spf1 include:zoho.eu include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.cums.net is "v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:[email protected]".
IPv4 address 104.20.38.8 answers for cums.net at resolver 1.1.1.1:53.
IPv4 address 172.66.149.177 answers for cums.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:10::6814:2608 answers for cums.net at resolver 1.1.1.1:53.
IPv6 address 2606:4700:10::ac42:95b1 answers for cums.net at resolver 1.1.1.1:53.
Mail exchanger mx.zoho.eu has preference 10.
Mail exchanger mx2.zoho.eu has preference 20.
Mail exchanger mx3.zoho.eu has preference 30.
Hosting and geo
cums.net is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.20.38.8 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for cums.net is valid, with 83 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | cums.net |
| Valid from | 24 October 2026 |
| Valid until | 22 January 2027 |
| Days left | 83 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: cums.net, worker.cums.net.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- Cloudflare · CDN
- HTTP/3 · Miscellaneous
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
On-page checks
The homepage returned HTTP 403 in 26 ms. The target title is 27 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 26 ms |
| Title length | 27 yes |
| Quoted title | "Quick security check | CUMS" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | noindex,nofollow |
| Canonical | — |
| Language | en |
| 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 cums.net 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 cums.net. 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 15 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 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
First checked on 30 October 2026; changes will appear here.
Questions
Is cums.net safe?
Cloudflare family DNS returned a block for cums.net. That resolver covers adult and malware names.
Who hosts cums.net?
cums.net is placed in Toronto, Canada.
When does cums.net expire?
cums.net expires on 11 March 2028 according to https://rdap.verisign.com/net/v1/domain/cums.net.
Who owns cums.net?
The registry did not return a person or a company for cums.net. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/net/v1/domain/cums.net at 2026-10-30T14:51:30Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:51:30Z
- TLS source tls:443 at 2026-10-30T14:51:30Z
- HTTP source https://cums.net/ at 2026-10-30T14:51:30Z
- Tech source wappalyzergo at 2026-10-30T14:51:30Z
- Geo source db-ip at 2026-10-30T14:51:30Z
- Safety source family DNS and local lists at 2026-10-30T14:51:30Z
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.