near.org Near.org

   
NEAR | The OS for an Open Web

Domain Summary

What is the traffic rank for Near.org?

• Near.org ranks #198,537 globally on HypeStat.

What percent of global Internet users visit Near.org?

0.0006879% of global Internet users visit Near.org

How many people visit Near.org each day?

• Near.org receives approximately 33.9K visitors and 119,613 page impressions per day.

Which countries does Near.org receive most of its visitors from?

• Near.org is mostly visited by people located in United States,India,Viet Nam.

How much Near.org can earn?

• Near.org should earn about $369.17/day from advertising revenue.

What is Near.org estimated value?

• Estimated value of Near.org is $393,362.82.

What IP addresses does Near.org resolve to?

• Near.org resolves to the IP addresses 76.76.21.21.

Where are Near.org servers located in?

• Near.org has servers located in Walnut, California, 91789, United States.

near.org Profile

Title:NEAR | The OS for an Open Web
Description:"NEAR isn’t just a Layer 1 blockchain — it’s the Blockchain Operating System for an Open Web. Create and discover decentralized apps, and help build the future of the web, today."
Tags:
Category:Finance / Other Finance
About: Near is an open source public blockchain platform that enables developers to build and deploy decentralized applications. It is designed to provide scalability, low fees, and other features required for building applications with millions of users. Near also provides tools for developers to manage accounts, deploy contracts and interact with smart contracts. The platform also includes a decentralized application store for users to find and use applications.
*This text is generated by artificial intelligence and may not be accurate. Edit Site Info

What technologies does near.org use?

These are the technologies used at near.org. near.org has a total of 7 technologies installed in 6 different categories.

near.org Traffic Analysis

Near.org is ranked #198,537 in the world. This website is viewed by an estimated 33.9K visitors daily, generating a total of 119.6K pageviews. This equates to about 1M monthly visitors. Near.org traffic has decreased by 4.35% compared to last month.
Daily Visitors33.9K
5.9%
Monthly Visits1M
4.35%
Pages per Visit3.53
18.26%
Visit duration02:45
8.9%
Bounce Rate58.13%
13.04%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
33,912
Monthly Visits:
1,027,534
Pages per Visit:
3.53
Daily Pageviews:
119,613
Avg. visit duration:
02:45
Bounce rate:
58.13%
Global Reach:
0.0006879%
Monthly Visits (SEMrush):
873,962
Monthly Unique Visitors (SEMrush):
375,190
Monthly Visits (SimilarWeb):
1,027,629
HypeRank:
198,537
SEMrush Rank:
105,569
SimilarWeb Rank:
58,070
*All traffic values are estimates only.

Traffic sources

Direct:
62.07%
Referral:
24.99%
Search:
9.09%
Social:
3.85%
Paid:
0%

Desktop vs Mobile

Desktop:
29.20%
Mobile:
70.80%

Total Visits Last 3 Months

707.8K
NOV
1.1M
DEC
1M
JAN

Visitors by country

Country
Users%
 
United States 9.14%
 
India 8.55%
 
Viet Nam 7.73%
 
Indonesia 6.65%
 
France 5.80%

Where do visitors go on near.org?

 
Reach%Pageviews%PerUser
wallet.near.org
58.39%43.47%2.0
near.org
30.75%16.35%1.4
testnet.near.org
11.53%16.72%3.9
mainnet.near.org
8.77%7.22%2
explorer.near.org
6.29%4.14%2
Last update was 71 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with near.org in any way. Only publicly available statistics data are displayed.

Search Engine Indexes

Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.
Google Index:
14,100
Bing Index:
2,260
Baidu Index:
8

Moz Data

Domain Authority (DA) is a metric developed by Moz. DA is a score that predicts the ranking potential of a website on search engine result pages (SERPs). Moz calculates Domain Authority on a logarithmic scale from 1 to 100, with higher scores indicating a greater likelihood of ranking well in search results. Moz Domain Authority of near.org is 50.
Domain Authority:
  50
Page Authority:
  58
MozRank:
  6

 

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  near.org
Rank:
(Rank based on keywords, cost and organic traffic)
  105,569
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  3,466
Organic Traffic:
(Number of visitors coming from top 20 search results)
  16,077
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $10,907.00

Revenue report

Google.com would generate approximately $369.2 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $11.1K and annual gross revenue of approximately $134.7K. Based on these figures, the site's net worth is estimated at around $393.4K.

How much would near.org make?

Daily Revenue:
$369.17
Monthly Revenue:
$11,075.10
Yearly Revenue:
$134,747.05
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 10,937$52.82
 
Viet Nam 9,241$4.34
 
France 6,934$4.02
 
India 10,225$3.89
 
Indonesia 7,957$0.88

Loss of money due to Adblock?

Daily Revenue Loss:
$11.72
Monthly Revenue Loss:
$351.60
Yearly Revenue Loss:
$4,277.86
Daily Pageviews Blocked:
10,579
Monthly Pageviews Blocked:
317,365
Yearly Pageviews Blocked:
3,861,277

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 1,969$9.51
 
India 2,863$1.09
 
Indonesia 4,615$0.51
 
France 763$0.44
 
Viet Nam 370$0.17

How much is near.org worth?

Website Value:
$393.4K

Ad Experience Report

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
near.org
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
near.org
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report

Summary of the abusive experience rating of a website.
Root domain:
near.org
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is near.org hosted?

Near.org may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
76.76.21.21
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Walnut
California, CA
91789
United States, US
 

Other sites hosted on 76.76.21.21

How fast does near.org load?

The average loading time of near.org is 45 ms. The Desktop speed index is 62 and mobile speed index is 37.
Average Load Time:
45 ms

Page Speed (Google PageSpeed Insights) - Desktop

62
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)1.2s 86% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 86% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)12ms 91% of loads for this page have a fast (<100ms) First Input Delay (FID) 91% 4% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 4% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.3s 86% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 86% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)7ms 93% of loads for this page have a fast (<100ms) First Input Delay (FID) 93% 3% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 3% 3% of loads for this page have a slow (>300ms) First Input Delay (FID) 3%

Lab Data

First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 1,160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Speed Index 1.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets
Total Blocking Time 1,640 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Largest Contentful Paint 1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Time to Interactive 5.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric

Page Speed (Google PageSpeed Insights) - Mobile

37
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

First Contentful Paint (FCP)2.0s 86% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 72% 15% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 15% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
First Input Delay (FID)95ms 75% of loads for this page have a fast (<100ms) First Input Delay (FID) 75% 10% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 10% 14% of loads for this page have a slow (>300ms) First Input Delay (FID) 14%

Origin Data

All pages served from this origin have an SLOW speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

First Contentful Paint (FCP)1.9s 74% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 14% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 14% 11% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 11%
First Input Delay (FID)43ms 93% of loads for this page have a fast (<100ms) First Input Delay (FID) 81% 6% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 6% 12% of loads for this page have a slow (>300ms) First Input Delay (FID) 12%

Lab Data

Speed Index 6.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 27.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`  
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Max Potential First Input Delay 6,050 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Total Blocking Time 9,940 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Meaningful Paint 3.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint image was not lazily loaded  
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Largest Contentful Paint 7.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Preload Largest Contentful Paint image  
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Lazy load third-party resources with facades  
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn how to defer third-parties with a facade
Timing budget  
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more about performance budgets

Does near.org use compression?

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on near.org are reduced by 76%.
near.org use br compression.
Original size: 14.82 KB
Compressed size: 3.55 KB
File reduced by: 11.28 KB (76%)

Google Safe Browsing

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. near.org has 80 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  80
Safety Confidence:
  51

SSL Checker - SSL Certificate Verify

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. near.org supports HTTPS.
 near.org supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: near.org
Organization:
Location:
Issuer: R3
Valid from: Feb 9 06:02:23 2024 GMT
Valid until: May 9 06:02:22 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R3
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Sep 4 00:00:00 2020 GMT
Valid until: Sep 15 16:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 near.org supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.
access-control-allow-origin: *
age: 201359
cache-control: public, max-age=0, must-revalidate
content-disposition: inline
content-encoding: br
content-type: text/html; charset=utf-8
date: Sat, 02 Mar 2024 17:31:18 GMT
etag: W/"a1b96ed0ae7404a00f22ae7fb92e602b"
referrer-policy: strict-origin-when-cross-origin
server: Vercel
strict-transport-security: max-age=63072000
x-matched-path: /
x-vercel-cache: HIT
x-vercel-id: cle1::jfxvh-1709400678140-8ea38bf3fc9b

DNS Lookup

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
MX aspmx2.googlemail.com 3600
MX alt1.aspmx.l.google.com 3600
MX aspmx3.googlemail.com 3600
MX alt2.aspmx.l.google.com 3600
MX aspmx.l.google.com 3600
TXT knowbe4-site-verification=d12beda41529af4f156c57cd5cb851f5 3600
TXT MS=ms58296365 3600
TXT v=spf1 include:_spf.firebasemail.com ~all 3600
TXT firebase=pagoda-oboarding-dev 3600
TXT docusign=c9682d28-029c-4732-91af-79ff89ce583b 3600
TXT v=spf1 include:_spf.google.com ~all 3600
TXT google-site-verification=6ffovOmHVTm-4vkK5dLfrB7tF9zBPv-RzTwI53FLazU 3600
TXT ZOOM_verify_nyqc71LEk3M7osSupR2iAg 3600
TXT airtable-verification=791df4e56c51602a6455772c164502e1 3600
TXT 11705AE39E 3600
TXT miro-verification=0b44ddf2b3b7680dad19996edf6684f5f1701ea8 3600
TXT firebase=near-fastauth-prod 3600
TXT atlassian-domain-verification=lJhJEaavNaAd7TO764wCu4sGUx3xEXIjd4dMLNzWiq1wpmJypabadKoA2E8lp7rD 3600
SOA 21600
Mname ns-cloud-b1.googledomains.com
Rname cloud-dns-hostmaster.google.com
Serial Number 433
Refresh 21600
Retry 3600
Expire 259200
Minimum TTL 300
A 76.76.21.21 3533
NS ns-cloud-b1.googledomains.com 3533
NS ns-cloud-b4.googledomains.com 3533
NS ns-cloud-b3.googledomains.com 3533
NS ns-cloud-b2.googledomains.com 3533

Whois Lookup

Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on March 6, 2000 and will expire on March 6, 2024 if not renewed. This website is now assigned through the registrar Squarespace Domains II LLC. The WHOIS data for this website's domain was last updated on April 20, 2023.
Domain Created:
2000-03-06
Domain Expires:
2024-03-06
Domain Updated:
2023-04-20
Domain Age:
24 years 2 months 7 days
Domain Registrar:
Squarespace Domains II LLC
Domain Owner:
Contact Privacy Inc. Customer 7151571251
WhoIs:
 

Domain Name: near.org
Registry Domain ID: 41967250e68b4cfa835f3186cba29866-LROR
Registrar WHOIS Server: whois.squarespace.domains
Registrar URL: https://domains2.squarespace.com
Updated Date: 2023-04-20T13:58:03Z
Creation Date: 2000-03-06T13:57:52Z
Registrar Registration Expiration Date: 2024-03-06T13:57:52Z
Registrar: Squarespace Domains II LLC
Registrar IANA ID: 895
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.646-693-5324
Domain Status: clientTransferProhibited https://www.icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: Contact Privacy Inc. Customer 7151571251
Registrant Organization: Contact Privacy Inc. Customer 7151571251
Registrant Street: 96 Mowat Ave
Registrant City: Toronto
Registrant State/Province: ON
Registrant Postal Code: M4K 3K1
Registrant Country: CA
Registrant Phone: +1.4165385487
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: https://domains.google.com/contactregistrant?domain=near.org
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: Contact Privacy Inc. Customer 7151571251
Admin Organization: Contact Privacy Inc. Customer 7151571251
Admin Street: 96 Mowat Ave
Admin City: Toronto
Admin State/Province: ON
Admin Postal Code: M4K 3K1
Admin Country: CA
Admin Phone: +1.4165385487
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: https://domains.google.com/contactregistrant?domain=near.org
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: Contact Privacy Inc. Customer 7151571251
Tech Organization: Contact Privacy Inc. Customer 7151571251
Tech Street: 96 Mowat Ave
Tech City: Toronto
Tech State/Province: ON
Tech Postal Code: M4K 3K1
Tech Country: CA
Tech Phone: +1.4165385487
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: https://domains.google.com/contactregistrant?domain=near.org
Name Server: ns-cloud-b1.googledomains.com
Name Server: ns-cloud-b4.googledomains.com
Name Server: ns-cloud-b2.googledomains.com
Name Server: ns-cloud-b3.googledomains.com
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2024-03-02T17:31:24.166643Z