Clear.bank valuation and analysis

Robots.txt Information
Robot Path Permission
GoogleBot /
BingBot /
BaiduSpider /
YandexBot /
Meta Tags
Title ClearBank | Home
Description Financial institutions — from fintechs and digital asset platforms, to banks and credit unions — use our API to offer their customers fully regulated…
Keywords ClearBank,Accounts,Embedded Banking,Clearing,Clear payments,Virtual accounts,Real accounts,Operating accounts,Financial Services Compensation Scheme,FSCS,Clear Bank,UK payment schemes,Faster Payments,CHAPS,BACS,Connect to payment schemes,Payment schemes,Bank accounts,Payment rails,Business bank accounts
Server Information
WebSite clear favicon www.clear.bank
Host IP N/A
Location N/A
Related Websites
Site Rank
teamclearbanc.com #901,601
clearbanc.com #36,301
bcr-ltd.com #5,251,231
ppf.eu #2,935,728
More to Explore
clickbuyrewards.com
cinews.in
cliojournal.org
clickenergyni.com
cnkingjoy.com
coachingblog.lt
cobalto.media
cnmedios.com
coca-cola.lt
codexe.net
runa22.ru
rushcolefineart.com
Clear.bank Valuation
US$42,362
Last updated: Jul 22, 2024

Clear.bank has global traffic rank of 609,603 and ranks the 48,299th in Canada. Its global rank has gone down by 3,636 positions since 3 months ago. Clear.bank has an estimated worth of US$ 42,362, based on its estimated Ads revenue. Clear.bank receives approximately 5,158 unique visitors each day. According to SiteAdvisor, clear.bank is safe to visit.

Traffic & Worth Estimates
Purchase/Sale Value US$42,362
Daily Ads Revenue US$23
Monthly Ads Revenue US$696
Yearly Ads Revenue US$8,472
Daily Unique Visitors 5,158
Note: All traffic and earnings values are estimates.
Traffic Ranks
Global Rank 609,603
Delta (90 Days) ⬇️ 3,636
Most Popular In Country Canada
Country Rank 48,299
DNS Records
Host Type TTL Data
clear.bank A 3600 IP: 162.159.136.54
clear.bank A 3600 IP: 162.159.137.54
clear.bank MX 3600 Priority: 0
Target: clear-bank.mail.protection.outlook.com.
clear.bank NS 3600 Target: ns2.clear.bank.
clear.bank NS 3600 Target: ns3.clear.bank.
clear.bank NS 3600 Target: ns4.clear.bank.
clear.bank TXT 3600 TXT: spfmx1.domainkey.freshemail.io
clear.bank TXT 3600 TXT: v=spf1 include:sendgrid.net include:spf.protection.outlook.com include:mailgun.org ip4:80.169.171.34 include:fdspfeuc.freshemail.io include:_spf.salesforce.com -all
clear.bank TXT 3600 TXT: docusign=99a48d3d-c601-450e-84a0-082d42ca8e78
clear.bank TXT 3600 TXT: d365mktkey=usaxkexBc82OZphKyZ4TLoiOGp5v84s6kgAYKxPko58x
clear.bank TXT 3600 TXT: jvygnzrrqw268dqjfk5ljdqcgty8nrdw
clear.bank TXT 3600 TXT: docker-verification=244e2548-a586-48b0-a057-68cba2eacb24
clear.bank SOA 3600 MNAME: ns2.clear.bank.
RNAME: dnsmaster.clear.bank.
Serial: 3019
Refresh: 604800
Retry: 3600
Expire: 1209600
Minimum TTL: 300
HTTP Headers
HTTP/1.1 301 Moved Permanently
Date: Mon, 22 Jul 2024 21:30:02 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Location: https://clear.bank/
CF-Ray: 8a768794d8907cac-EWR
CF-Cache-Status: DYNAMIC
Set-Cookie: __cf_bm=mmgXk36MWZMMfianoru.PA11hgxvOQkQU3pHWNcdxFc-1721683802-1.0.1.1-qdZGmTWxpO_Dm8Kq0TJjrh91kbb3EOZAh9IAhSconPKOBygDZjRO9mVO07qOaODT2YOjXl8PhHm3yxpfsD.QYQ; path=/; expires=Mon, 22-Jul-24 22:00:02 GMT; domain=.clear.bank; HttpOnly
Server: cloudflare
alt-svc: h3=":443"; ma=86400

HTTP/2 200 
date: Mon, 22 Jul 2024 21:30:03 GMT
content-type: text/html; charset=UTF-8
cf-ray: 8a768796cd5218c0-EWR
cf-cache-status: DYNAMIC
cache-control: public, max-age=31536000, max-age=31536000
expires: Tue, 22 Jul 2025 21:30:02 GMT
strict-transport-security: max-age=31536000; includeSubDomains; preload
vary: Accept-Encoding
permissions-policy: geolocation=(), midi=(),sync-xhr=(),accelerometer=(), gyroscope=(), magnetometer=(), camera=(), fullscreen=(self)
referrer-policy: no-referrer-when-downgrade
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-powered-by: Craft CMS,Blitz
set-cookie: __cf_bm=DfQaXrvdBBrdG_3EOwu6AW_NJ0WnTi.yG3K8sKJ4oYU-1721683803-1.0.1.1-hH0X5Ra3g1abUw_nsS2ZJ5hnMQg1JJGQdb6bU1luYJZnXQaCd_jCM5niBetpNSUN4c4R9uihSGENZZ79a4nKLQ; path=/; expires=Mon, 22-Jul-24 22:00:03 GMT; domain=.clear.bank; HttpOnly; Secure; SameSite=None
server: cloudflare
alt-svc: h3=":443"; ma=86400

Clear.bank Whois Information
Domain Name: clear.bank
Registry Domain ID: 128177101_DOMAIN_BANK-NSR
Registrar WHOIS Server:
Registrar URL: www.lexsynergy.com
Updated Date: 2019-11-13T09:16:55Z
Creation Date: 2017-01-09T14:37:40Z
Registry Expiry Date: 2021-01-09T14:37:40Z
Registrar: Lexsynergy Limited
Registrar IANA ID: 1466
Registrar Abuse Contact Email: abuse@lexsynergy.com
Registrar Abuse Contact Phone: +44.2031370459
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Organization: Clearbank Limited
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: Norfolk
Registrant Postal Code:
Registrant Country: GB
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns2.clear.bank
Name Server: ns3.clear.bank
Name Server: ns4.clear.bank
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/

fTLD Registry Services, LLC (Registry Operator) is required to collect and 
provide domain name registration information (Whois Data) for a variety 
of purposes. Registry Operator through its Registry Service Provider enables 
access to Whois Data through a standard text-based network protocol on 
port 43 and as a standard web-based interface at whois.nic.bank. 
Both interfaces are publicly available at no cost to the user and are 
reachable worldwide. This service is available to any Internet user and its 
use does not require prior authorization or permission.

Registry Operator provides the public Whois Data for information purposes 
only, and does not guarantee its accuracy.

By accessing Whois Data made available by Registry Operator, you agree 
that you will use the Whois Data only for lawful purposes.  Under no 
circumstance shall the data or the systems of Registry Operator and/or 
Registry Service Provider be used to: allow, enable, or otherwise support the 
transmission of mass unsolicited, commercial advertising or solicitations via, 
email, telephone or facsimile; or enable high volume, automated, electronic 
processes that send queries or data to the systems of Registry Operator, 
Registry Service Provider, or Registrar except as reasonably necessary to 
register domain names or modify existing registrations. The compilation, 
repackaging, disseminations or other use of the Whois Data is expressly 
prohibited without the prior consent of Registry Operator. Registry Operator 
reserves the right to restrict third party access to Whois Data through these 
public resources in its sole discretion to ensure operational stability. Registry 
Operator may restrict or block access to Whois Data for failure to abide by 
the Terms of Use.

Notice:  The expiration data displayed in this record is the date the 
Registrars sponsorship of the domain name registration in is currently set to 
expire. This date does not necessarily reflect the expiration date of the 
domain name Registrants Registration Agreement with the sponsoring 
Registrar. Users may consult the sponsoring Registrars Whois Data to view 
the Registrars reported date of expiration for a specific domain name.