blurt.blog Blurt.blog

   
Blurt

Domain Summary

What is the traffic rank for Blurt.blog?

• Blurt.blog ranks #1,424,376 globally on HypeStat.

What percent of global Internet users visit Blurt.blog?

6.62E-5% of global Internet users visit Blurt.blog

How many people visit Blurt.blog each day?

• Blurt.blog receives approximately 3.3K visitors and 24,270 page impressions per day.

Which countries does Blurt.blog receive most of its visitors from?

• Blurt.blog is mostly visited by people located in United States,Bosnia and Herzegovina,Canada.

How much Blurt.blog can earn?

• Blurt.blog should earn about $102.09/day from advertising revenue.

What is Blurt.blog estimated value?

• Estimated value of Blurt.blog is $96,382.76.

What IP addresses does Blurt.blog resolve to?

• Blurt.blog resolves to the IP addresses 104.21.48.1.

Where are Blurt.blog servers located in?

• Blurt.blog has servers located in United States.

blurt.blog Profile

Title:Blurt Description:Blurt is a social media platform where everyone gets paid for creating and curating content. It leverages a robust digital points system (Blurt) for digital rewards.
Category:Finance / Other Finance

What technologies does blurt.blog use?

These are the technologies used at blurt.blog. blurt.blog has a total of 8 technologies installed in 6 different categories.

blurt.blog Traffic Analysis

Blurt.blog is ranked #1,424,376 in the world. This website is viewed by an estimated 3.3K visitors daily, generating a total of 24.3K pageviews. This equates to about 98.9K monthly visitors. Blurt.blog traffic has increased by 36.38% compared to last month.
Daily Visitors3.3K
59.23%
Monthly Visits98.9K
36.38%
Pages per Visit7.43
38.77%
Visit duration08:02
39.41%
Bounce Rate26.39%
21.11%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
3,265
Monthly Visits:
98,930
Pages per Visit:
7.43
Daily Pageviews:
24,270
Avg. visit duration:
08:02
Bounce rate:
26.39%
Global Reach:
6.62E-5%
Monthly Visits (SEMrush):
25,028
Monthly Unique Visitors (SEMrush):
16,975
Monthly Visits (SimilarWeb):
99,945
HypeRank:
1,424,376
SEMrush Rank:
2,084,539
SimilarWeb Rank:
261,642
*All traffic values are estimates only.

Traffic sources

Direct:
66.01%
Referral:
1.06%
Search:
32.31%
Social:
0.23%
Paid:
0.39%

Desktop vs Mobile

Desktop:
47.06%
Mobile:
52.94%

Total Visits Last 3 Months

46.3K
APR
72.5K
MAY
98.9K
JUN

Visitors by country

Country
Users%
 
United States 67.06%
 
Bosnia and Herzegovina 10.04%
 
Canada 7.62%
 
Poland 1.75%
 
India 1.61%

Where do visitors go on blurt.blog?

 
Reach%Pageviews%PerUser
blurt.blog
100.00%100.00%3.8

Which sites are competitors to blurt.blog?

Websites similar to blurt.blog are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Domain
CompareDaily Visitors
peakd.com
Compare >16.9K
hive.blog
Compare >10.3K
Last update was 4 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with blurt.blog 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:
166,000
Bing Index:
670,000
Baidu Index:
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:
  blurt.blog
Rank:
(Rank based on keywords, cost and organic traffic)
  2,084,539
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  3,975
Organic Traffic:
(Number of visitors coming from top 20 search results)
  315
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $6.00

Revenue report

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

How much would blurt.blog make?

Daily Revenue:
$102.09
Monthly Revenue:
$3,062.70
Yearly Revenue:
$37,262.85
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 16,276$78.61
 
Canada 1,850$11.18
 
Bosnia and Herzegovina 2,437$0.19
 
Poland 425$0.17
 
India 391$0.15

Loss of money due to Adblock?

Daily Revenue Loss:
$17.07
Monthly Revenue Loss:
$512.25
Yearly Revenue Loss:
$6,232.33
Daily Pageviews Blocked:
4,056
Monthly Pageviews Blocked:
121,691
Yearly Pageviews Blocked:
1,480,580

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 2,930$14.15
 
Canada 463$2.79
 
Poland 140$0.06
 
India 110$0.04
 
Bosnia and Herzegovina 414$0.03

How much is blurt.blog worth?

Website Value:
$96.4K

Ad Experience Report

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

Mobile summary

Root domain:
blurt.blog
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:
blurt.blog
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:
blurt.blog
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 blurt.blog hosted?

Blurt.blog may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
104.21.48.1
ASN:
AS13335 
ISP:
Cloudflare Inc 
Server Location:

United States, US
 

Other sites hosted on 104.21.48.1

How fast does blurt.blog load?

The average loading time of blurt.blog is 2105 ms. The Desktop speed index is 0 and mobile speed index is 32.
Average Load Time:
2105 ms

Page Speed (Google PageSpeed Insights) - Mobile

32
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.

Cumulative Layout Shift (CLS)11ms 0% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 72% 15% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 15% 11% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 11%
Time To First Byte (TTFB)1.2s 0% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 64% 23% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 23% 12% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 12%
First Contentful Paint (FCP)2.1s 0% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 67% 18% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 18% 13% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 13%
First Input Delay (FID)53ms 82% of loads for this page have a fast (<100ms) First Input Delay (FID) 82% 7% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 7% 9% of loads for this page have a slow (>300ms) First Input Delay (FID) 9%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)3.9s 0% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 57% 18% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 18% 23% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 23%

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.

Cumulative Layout Shift (CLS)11ms 72% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 72% 15% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 15% 11% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 11%
Time To First Byte (TTFB)1.2s 64% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 64% 23% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 23% 12% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 12%
First Contentful Paint (FCP)2.1s 67% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 67% 18% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 18% 13% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 13%
First Input Delay (FID)53ms 0% of loads for this page have a fast (<100ms) First Input Delay (FID) 82% 7% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 7% 9% of loads for this page have a slow (>300ms) First Input Delay (FID) 9%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)3.9s 57% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 57% 18% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 18% 23% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 23%

Lab Data

Time to Interactive 18.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Total Blocking Time 1,610 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Avoids `unload` event listeners  
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
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
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Max Potential First Input Delay 2,160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
First Contentful Paint 3.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
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 more
First Contentful Paint (3G) 6390 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
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
Speed Index 10.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Largest Contentful Paint 3.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more

Does blurt.blog 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 blurt.blog are reduced by 78%.
blurt.blog use br compression.
Original size: 733.68 KB
Compressed size: 156.99 KB
File reduced by: 576.69 KB (78%)

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.
Status:
  SAFE

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. blurt.blog supports HTTPS.
 blurt.blog supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: blurt.blog
Organization:
Location:
Issuer: WE1
Valid from: Jul 14 05:03:57 2025 GMT
Valid until: Oct 12 06:02:18 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: WE1
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Common Name: GTS Root R4
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize:

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.
 blurt.blog 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.
date: Tue, 15 Jul 2025 19:15:22 GMT
content-type: text/html; charset=utf-8
access-control-allow-headers: Content-Type
access-control-allow-methods: POST, GET, OPTIONS
access-control-allow-origin: *
alt-svc: h3=":443"; ma=86400
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=QoKsYpm7WJ%2BoRNYYkBOHHlzuaLc%2BG9jzocdS53PrVOW%2F%2BwWCdflQIeserIr4gGxl%2Fna7uSYwcXLljCue7h7jd5D0PJMsoedGETiShoZsyew3TYmkjeY%3D"}]}
vary: accept-encoding
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
via: 1.1 Caddy
x-upstream: 127.0.0.1:4080
cf-cache-status: DYNAMIC
content-encoding: br
server: cloudflare
set-cookie: blurt-dev=crypto-session:XccMBSN9DJdNEFqabtyjIAcV1ibAPM9DyCIK6JNtZ7kwmxJUf9D5mmVvgTPvcV06Aq74iC83qimr9iGDPa2jDxd+WEVif7zNv9j9wyD8jnaODIeeCqM58I4DTwgTEZ9SxIufmF2DC6jqawKa5dq90dgkucgC9W5TvHtcEjEEss3en6U5rUy9Vsjj2U1FQsmzsG8pN9V1YD/YvYGjVe+5DrlIDlO+ExRgqRFNkr6JH2i2LVPsVAA1DCYWqlCniWI5Yb3JqIhn85AHD43ZJ6GLZgu4t4AWsIZFnWnNQdQc84vzoPSYMux7kGpYqBdBL5WwgLvkeVLaMwOYbk6xFUiu7xYztV6foS2HnU5/Yg9ZKKhj047c0aU=; HttpOnly; Path=/; Expires=Sat, 13 Sep 2025 19:15:22 GMT
set-cookie: blurt-dev.sig=WR45AX3voeYdLmWLQREAZ9hic3w; HttpOnly; Path=/; Expires=Sat, 13 Sep 2025 19:15:22 GMT
cf-ray: 95fb9682cbb065bc-FRA

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
HINFO 3600

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 April 13, 2020 and will expire on April 13, 2026 if not renewed. This website is now assigned through the registrar Go Daddy, LLC. The WHOIS data for this website's domain was last updated on June 8, 2025.
Domain Created:
2020-04-13
Domain Expires:
2026-04-13
Domain Updated:
2025-06-08
Domain Age:
5 years 3 months 6 days
Domain Registrar:
Go Daddy, LLC
Domain Owner:
Domains By Proxy, LLC
WhoIs:
 

Domain Name: blurt.blog
Registry Domain ID: 648649-BLOG
Registrar WHOIS Server: https://www.godaddy.com/whois
Registrar URL: https://www.godaddy.com/
Updated Date: 2025-06-08T16:20:54Z
Creation Date: 2020-04-13T03:10:15Z
Registry Expiry Date: 2026-04-13T23:59:59Z
Registrar: Go Daddy, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Domains By Proxy, LLC
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: Arizona
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: US
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Registry Billing ID: REDACTED FOR PRIVACY
Billing Name: REDACTED FOR PRIVACY
Billing Organization: REDACTED FOR PRIVACY
Billing Street: REDACTED FOR PRIVACY
Billing City: REDACTED FOR PRIVACY
Billing State/Province: REDACTED FOR PRIVACY
Billing Postal Code: REDACTED FOR PRIVACY
Billing Country: REDACTED FOR PRIVACY
Billing Phone: REDACTED FOR PRIVACY
Billing Phone Ext: REDACTED FOR PRIVACY
Billing Fax: REDACTED FOR PRIVACY
Billing Fax Ext: REDACTED FOR PRIVACY
Billing Email: Please ask the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Other contacts of the queried domain name
Name Server: conrad.ns.cloudflare.com
Name Server: suzanne.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2025-07-09T17:43:56Z