anchor.fm Anchor.fm

   
Spotify for Podcasters

Domain Summary

What is the traffic rank for Anchor.fm?

• Anchor.fm ranks #760,936 globally on HypeStat.

What percent of global Internet users visit Anchor.fm?

• 0.0004322% of global Internet users visit Anchor.fm

How many people visit Anchor.fm each day?

• Anchor.fm receives approximately 21.3K visitors and 28,317 page impressions per day.

Which countries does Anchor.fm receive most of its visitors from?

• Anchor.fm is mostly visited by people located in United States,Russian Federation,United Kingdom.

How much Anchor.fm can earn?

• Anchor.fm should earn about $105.67/day from advertising revenue.

What is Anchor.fm estimated value?

• Estimated value of Anchor.fm is $98,118.37.

What IP addresses does Anchor.fm resolve to?

• Anchor.fm resolves to the IP addresses 151.101.66.133.

Where are Anchor.fm servers located in?

• Anchor.fm has servers located in Ashburn, Virginia, 20149, United States.

anchor.fm Profile

Title:Spotify for Podcasters
Description:Get to know Spotify for Podcasters, the free, all-in-one podcast platform for every creator.
Tags:
podcast
public radio
startup
talk radio
microphone
audio clip
podcast hosting
making a podcast
sponsor a podcast
npr
voice
free podcast hosting
creating a podcast
conversation
talk
audio
podcast sponsorships
make a podcast
podcast creation
anchor
Category:Arts and Entertainment / Other Arts and Entertainment
About: Create, distribute, host, and monetize your podcast, 100% free. Edit Site Info

What technologies does anchor.fm use?

These are the technologies used at anchor.fm. anchor.fm has a total of 8 technologies installed in 7 different categories.
Reverse proxies
Envoy Envoy
Security
HSTS HSTS
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
webpack webpack
Web Frameworks
Next.js Next.js
Web Servers
Next.js Next.js
JavaScript Frameworks
React React
Programming Languages
Node.js Node.js

anchor.fm Traffic Analysis

Anchor.fm is ranked #760,936 in the world. This website is viewed by an estimated 21.3K visitors daily, generating a total of 28.3K pageviews. This equates to about 645.6K monthly visitors. Anchor.fm traffic has decreased by 30.6% compared to last month.
Daily Visitors21.3K
16.34%
Monthly Visits645.6K
30.6%
Pages per Visit1.33
13.36%
Visit duration00:53
309.86%
Bounce Rate80.40%
4.68%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
21,306
Monthly Visits:
645,572
Pages per Visit:
1.33
Daily Pageviews:
28,317
Avg. visit duration:
00:53
Bounce rate:
80.40%
Global Reach:
0.0004322%
Monthly Visits (SEMrush):
1,053,126
Monthly Unique Visitors (SEMrush):
691,149
Monthly Visits (SimilarWeb):
632,852
HypeRank:
760,936
SEMrush Rank:
718,121
SimilarWeb Rank:
128,921
*All traffic values are estimates only.

Traffic sources

Direct:
88.59%
Referral:
5.01%
Search:
0.21%
Social:
6.18%
Paid:
0%

Desktop vs Mobile

Desktop:
7.28%
Mobile:
92.72%

Total Visits Last 3 Months

625.5K
JAN
0.9M
FEB
645.6K
MAR

Visitors by country

Country
Users%
 
United States 27.95%
 
Russian Federation 6.47%
 
United Kingdom 6.38%
 
Netherlands 5.62%
 
Germany 4.08%

Where do visitors go on anchor.fm?

 
Reach%Pageviews%PerUser
anchor.fm
98.62%96.67%2.65
help.anchor.fm
3.27%2.43%2.0
blog.anchor.fm
2.04%0.90%1.2
OTHER
0%0.01%0
Last update was 28 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with anchor.fm 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:
87
Bing Index:
2,580

  ▼

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:
  anchor.fm
Rank:
(Rank based on keywords, cost and organic traffic)
  718,121
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  3,041
Organic Traffic:
(Number of visitors coming from top 20 search results)
  1,472
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $2,467.00
Full SEMrush Report >>

Revenue report ▼

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

How much would anchor.fm make?

Daily Revenue:
$105.67
Monthly Revenue:
$3,170.10
Yearly Revenue:
$38,569.55
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 7,914$38.23
 
United Kingdom 1,806$4.84
 
Netherlands 1,591$3.04
 
Germany 1,156$1.62
 
Russian Federation 1,831$0.75

Loss of money due to Adblock?

Daily Revenue Loss:
$8.69
Monthly Revenue Loss:
$260.58
Yearly Revenue Loss:
$3,170.42
Daily Pageviews Blocked:
2,429
Monthly Pageviews Blocked:
72,873
Yearly Pageviews Blocked:
886,623

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 1,425$6.88
 
United Kingdom 289$0.77
 
Netherlands 271$0.52
 
Germany 335$0.47
 
Russian Federation 110$0.05

How much is anchor.fm worth?

Website Value:
$98.1K

Ad Experience Report ▼

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

Mobile summary

Root domain:
anchor.fm
Last Change Time:
(The last time that the site changed status.)
2019-05-24 16:01:34
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.)
Passing

Desktop summary

Root domain:
anchor.fm
Last Change Time:
(The last time that the site changed status.)
2019-05-24 16:01:34
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.)
Passing

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
anchor.fm
Last Change Time:
(The last time that the site changed status.)
2019-05-24 16:01:34
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.)
Passing

Where is anchor.fm hosted? ▼

Anchor.fm may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
151.101.66.133
ASN:
AS54113 
ISP:
Fastly 
Server Location:
Ashburn
Virginia, VA
20149
United States, US
 

Other sites hosted on 151.101.66.133

How fast does anchor.fm load? ▼

The average loading time of anchor.fm is 217 ms. The Desktop speed index is 48 and mobile speed index is 61.
Average Load Time:
217 ms

Page Speed (Google PageSpeed Insights) - Desktop

48
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)2.1s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 68% 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)4ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

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.6s 78% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 78% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)8ms 91% of loads for this page have a fast (<100ms) First Input Delay (FID) 91% 3% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 3% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%

Lab Data

Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Contentful Paint 1.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful 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
Total Blocking Time 720 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Max Potential First Input Delay 350 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
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
Largest Contentful Paint 4.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
Time to Interactive 3.6 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
First Meaningful Paint 1.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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

Page Speed (Google PageSpeed Insights) - Mobile

61
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.3s 68% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 87% 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)26ms 87% of loads for this page have a fast (<100ms) First Input Delay (FID) 87% 7% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 7% 4% of loads for this page have a slow (>300ms) First Input Delay (FID) 4%

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)2.5s 62% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 62% 18% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 18% 19% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 19%
First Input Delay (FID)55ms 91% of loads for this page have a fast (<100ms) First Input Delay (FID) 78% 6% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 6% 14% of loads for this page have a slow (>300ms) First Input Delay (FID) 14%

Lab Data

Total Blocking Time 3,850 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
Speed Index 7.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Meaningful Paint 1.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint 1.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Time to Interactive 21.0 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

Does anchor.fm 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 anchor.fm are reduced by 83%.
anchor.fm use gzip compression.
Original size: 218.4 KB
Compressed size: 35.21 KB
File reduced by: 183.2 KB (83%)

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. anchor.fm has 61 Safety Reputations.
Status:
  SAFE
Safety Reputations:
  61
Safety Confidence:
  2

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. anchor.fm supports HTTPS.
 anchor.fm supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.spotify.com
Organization: Spotify AB
Location: Stockholm, SE
Issuer: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from: Feb 5 00:00:00 2024 GMT
Valid until: Feb 4 23:59:59 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: DigiCert Global G2 TLS RSA SHA256 2020 CA1
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root G2
Valid from: Mar 30 00:00:00 2021 GMT
Valid until: Mar 29 23:59:59 2031 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.
 anchor.fm 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. 
server: Varnish
retry-after: 0
x-isc: 620
location: https://podcasters.spotify.com
accept-ranges: bytes
date: Wed, 10 Apr 2024 12:51:36 GMT
via: 1.1 varnish
x-served-by: cache-chi-klot8100023-CHI
x-cache: HIT
x-cache-hits: 0
x-timer: S1712753496.148803,VS0,VE0
strict-transport-security: max-age=86400
content-length: 52

HTTP/2 200 
server: envoy
date: Wed, 10 Apr 2024 12:51:36 GMT
content-type: text/html; charset=utf-8
vary: Accept-Encoding,Accept-Encoding
set-cookie: sp_t=4486bb18-e3c7-4a01-b834-a088ae87e57b; Expires=Fri, 11 Apr 2025 12:51:36 GMT
x-powered-by: Next.js
cache-control: private, no-cache, no-store, max-age=0, must-revalidate
content-encoding: gzip
strict-transport-security: max-age=31536000
x-content-type-options: nosniff
via: HTTP/2 edgeproxy, 1.1 google
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

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
TXT gFouYHTz 60
TXT google-site-verification=oQgtxy9CVzwVG5N24HvI7zyzd-6BkZFBaJZFDfohex0 60
TXT pdy5pt605k4w849s6sk3r0gwj9z29gqk 60
TXT v=spf1 a mx include:_spf.google.com include:amazonses.com -all 60
TXT google-site-verification=ZkLGP8hTP-T_uEkUYXu5CvOAaT1JMKQev5jOGLRsW_A 60
TXT c7bd157xh82z5wwqphr8hmr018bbzr9q 60
MX aspmx.l.google.com 3600
MX aspmx4.googlemail.com 3600
MX aspmx5.googlemail.com 3600
MX aspmx2.googlemail.com 3600
MX alt1.aspmx.l.google.com 3600
MX aspmx3.googlemail.com 3600
MX alt2.aspmx.l.google.com 3600
SOA 900
Mname ns-533.awsdns-02.net
Rname awsdns-hostmaster.amazon.com
Serial Number 1
Refresh 7200
Retry 900
Expire 1209600
Minimum TTL 86400
A 151.101.130.133 45
A 151.101.194.133 45
A 151.101.2.133 45
A 151.101.66.133 45
NS ns-1884.awsdns-43.co.uk 3600
NS ns-203.awsdns-25.com 3600
NS ns-533.awsdns-02.net 3600
NS ns-1225.awsdns-25.org 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 February 6, 2015 and will expire on February 6, 2025 if not renewed. This website is now assigned through the registrar Ports Group AB. The WHOIS data for this website's domain was last updated on December 12, 2023.
Domain Created:
2015-02-06
Domain Expires:
2025-02-06
Domain Updated:
2023-12-12
Domain Age:
9 years 3 months 3 days
Domain Registrar:
Ports Group AB
WhoIs:
 

Domain Name: ANCHOR.FM
Registry Domain ID: D34835514-CNIC
Registrar WHOIS Server: whois.abion.com
Registrar URL: http://www.abion.com
Updated Date: 2023-12-12T13:27:11.0Z
Creation Date: 2015-02-06T23:59:59.0Z
Registry Expiry Date: 2025-02-06T23:59:59.0Z
Registrar: Ports Group AB
Registrar IANA ID: 73
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registrant Email: https://whois.nic.fm/contact/anchor.fm/registrant
Admin Email: https://whois.nic.fm/contact/anchor.fm/admin
Tech Email: https://whois.nic.fm/contact/anchor.fm/tech
Name Server: NS-533.AWSDNS-02.NET
Name Server: NS-203.AWSDNS-25.COM
Name Server: NS-1884.AWSDNS-43.CO.UK
Name Server: NS-1225.AWSDNS-25.ORG
DNSSEC: unsigned
Billing Email: https://whois.nic.fm/contact/anchor.fm/billing
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +46.317202000
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2024-04-10T12:51:08.0Z > IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit
https://www.centralnic.com/support/rdap