channelcrawler.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 32 days left13 years old
85
channelcrawler.com was registered on 13 Oct 2013 via Key-Systems GmbH and the registry expiry is 13 Oct 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/channelcrawler.com.
channelcrawler.com publishes 2 nameservers. DNSSEC is not signed.
channelcrawler.com has 2 IPv4 addresses (199.60.103.176, 199.60.103.76). The geolocation database places 199.60.103.176 in Cambridge (East Cambridge), United States.
The TLS certificate from YE1 is valid and has 32 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Alpine.js, Cloudflare, Cloudflare Bot Management, Google Analytics, HSTS, HTTP/3, HubSpot, HubSpot CMS Hub, Tailwind CSS and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for channelcrawler.com in the checks that ran.
Domain · RDAP/WHOIS
channelcrawler.com was registered on 13 Oct 2013 via Key-Systems GmbH. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/channelcrawler.com.
| Registered | since 13 Oct 2013 |
|---|---|
| Created | 13 October 2013 |
| Updated | 14 October 2026 |
| Expires | 13 October 2027 |
| Registrar | Key-Systems GmbH |
| Status | client transfer prohibited |
| Nameservers | eleanor.ns.cloudflare.com, ruben.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/channelcrawler.com |
channelcrawler.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 eleanor.ns.cloudflare.com is published for channelcrawler.com in the registration record from https://rdap.verisign.com/com/v1/domain/channelcrawler.com.
Nameserver ruben.ns.cloudflare.com is published for channelcrawler.com in the registration record from https://rdap.verisign.com/com/v1/domain/channelcrawler.com.
DNS
channelcrawler.com has 2 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 199.60.103.176, 199.60.103.76 |
|---|---|
| AAAA | — |
| NS | eleanor.ns.cloudflare.com, ruben.ns.cloudflare.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at channelcrawler.com is "v=spf1 include:_spf.transip.email ip4:85.10.137.143 include:_spf.google.com include:_spf.google.com ~all".
The DMARC text record at _dmarc.channelcrawler.com is "v=DMARC1; p=none;".
IPv4 address 199.60.103.176 answers for channelcrawler.com at resolver 1.1.1.1:53.
IPv4 address 199.60.103.76 answers for channelcrawler.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
A random label under channelcrawler.com also resolved, which means wildcard DNS is on.
Hosting and geo
channelcrawler.com is placed in Cambridge (East Cambridge), United States by the local geolocation database (db-ip).
| Address | 199.60.103.176 |
|---|---|
| Country | United States |
| City | Cambridge (East Cambridge) |
| Source | db-ip |
SSL/TLS
The certificate for channelcrawler.com is valid, with 32 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | c4d3606e.sni.cloudflaressl.com |
| Valid from | 3 September 2026 |
| Valid until | 2 December 2026 |
| Days left | 32 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: c4d3606e.sni.cloudflaressl.com, channelcrawler.com.
Tech stack
Tech detection checked the fetched homepage and named 10 products. Source: wappalyzergo.
- Alpine.js · JavaScript frameworks
- Cloudflare · CDN
- Cloudflare Bot Management · Security
- Google Analytics · Analytics
- HSTS · Security
- HTTP/3 · Miscellaneous
- HubSpot · Marketing automation
- HubSpot CMS Hub · CMS
- Tailwind CSS · UI frameworks
- jsDelivr · CDN
Alpine.js is filed under JavaScript frameworks.
Cloudflare is filed under CDN.
Cloudflare Bot Management is filed under Security.
Google Analytics is filed under Analytics.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
HubSpot is filed under Marketing automation.
HubSpot CMS Hub is filed under CMS.
Tailwind CSS is filed under UI frameworks.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 36 ms. The target title is 65 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 36 ms |
| Title length | 65 no |
| Quoted title | "Largest YouTube Channel and Sponsorship Database | ChannelCrawler" |
| Meta description | "Find YouTube sponsorship opportunities across 35M+ searchable channels. Discover creators and sponsoring brands, export shortlists, and connect via API." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://channelcrawler.com |
| Language | en |
| Links | 64 |
| Images | 103 |
| 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 channelcrawler.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 | yes |
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 10 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 10 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 Cambridge (East Cambridge).
- October 2026: geo country changed from empty to United States.
Questions
Is channelcrawler.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 channelcrawler.com?
channelcrawler.com is placed in Cambridge (East Cambridge), United States.
When does channelcrawler.com expire?
channelcrawler.com expires on 13 October 2027 according to https://rdap.verisign.com/com/v1/domain/channelcrawler.com.
Who owns channelcrawler.com?
The registry did not return a person or a company for channelcrawler.com. RDAP often redacts the registrant. The registrar on file is Key-Systems GmbH.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/channelcrawler.com at 2026-10-30T13:49:16Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:49:16Z
- TLS source tls:443 at 2026-10-30T13:49:16Z
- HTTP source https://channelcrawler.com/ at 2026-10-30T13:49:16Z
- Tech source wappalyzergo at 2026-10-30T13:49:16Z
- Geo source db-ip at 2026-10-30T13:49:16Z
- Safety source family DNS and local lists at 2026-10-30T13:49:16Z
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.