api.storage

Api.storage

#2,883,044 Global
403 - Forbidden: Access is denied.
Last Updated 579 days ago
     
This can take up to 60 seconds. Please wait...

Domain Summary

What is the traffic rank for Api.storage?

Api.storage ranks #2,883,044 globally on HypeStat.

What percent of global Internet users visit Api.storage?

<0.000001% of global Internet users visit Api.storage

How many people visit Api.storage each day?

Api.storage receives approximately 3 visitors and 3 page impressions per day.

How much Api.storage can earn?

Api.storage should earn about $0.01/day from advertising revenue.

What is Api.storage estimated value?

Estimated value of Api.storage is $1.62.

What IP addresses does Api.storage resolve to?

Api.storage resolves to the IP addresses 104.18.39.173.

api.storage Profile

Title
403 - Forbidden: Access is denied.

api.storage Traffic Analysis

Api.storage is ranked #2,883,044 in the world. This website is viewed by an estimated 3 visitors daily, generating a total of 3 pageviews. This equates to about 90.9 monthly visitors. Api.storage traffic has decreased by 75.85% compared to last month.

Daily Visitors
3
3 unique
▼ 27.56%
Monthly Visits
90.9
▼ 75.85%
Daily Pageviews
3
3 pageviews
Pages per Visit
1.00
▼ 40%
Visit Duration
n/a
▼ 100%
Bounce Rate
100.00%
▲ 200.03%
Daily Unique Visitors
3
Monthly Visits
91
Pages per Visit
1.00
Daily Pageviews
3
Avg. Visit Duration
n/a
Bounce Rate
100.00%
Global Reach
<0.000001%
Monthly Visits (SEMrush)
92
Monthly Unique Visitors (SEMrush)
92
HypeRank
2,883,044

*All traffic values are estimates only.

Traffic Sources

Direct100.00%
Referral0%
Search0%
Social0%
Paid0%

Desktop vs Mobile

Desktop
100.00%
Mobile
0%

Monthly Visits

376
JAN '25
91
FEB '25
SEO

api.storage SEMrush Overview

SEMrush is a complete online advertising and marketing platform that gives a wide variety of tools and features to help businesses and marketers improve their online visibility and optimize their digital marketing strategies.

SemRushSemRush
Domain
api.storage
RankBased on keywords, cost and organic traffic
n/a
Organic KeywordsKeywords in top 20 Google SERP
0
Organic TrafficVisitors coming from top 20 search results
0
Organic CostEquivalent Google Ads spend for the same traffic
$0.00
Full SEMrush Report →

Search Engine Indexes

Search engine indexes are huge databases of web pages that search engines like Google and Baidu use to retrieve relevant results when users search. These indexes are built by crawling and indexing pages from across the web.

Google Index
1
Monetization

Revenue Report

api.storage would generate approximately $0 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $0.3 and annual gross revenue of approximately $3.7. Based on these figures, the site's net worth is estimated at around $1.6.

How much would api.storage make?

Daily Revenue
$0.01
Monthly Revenue
$0.30
Yearly Revenue
$3.65

How much is api.storage worth?

Website Value
$1.6

*All earnings values are estimates only.

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to api.storage, per platform.

Mobile Summary

Root Domain
api.storage
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Desktop Summary

Root Domain
api.storage
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Abusive Experience

Root Domain
api.storage
EnforcementChrome is not preventing your site from opening new windows or tabs.
Off
StatusReviewed for abusive experiences
Not reviewed
Technical

Where is api.storage hosted?

Api.storage is behind Cloudflare (CDN and security proxy). Visitors connect to Cloudflare's shared IP addresses, which answer from the nearest Cloudflare data center, so the real server location is hidden.

Server IP
104.18.39.173
ISP
Cloudflare, Inc. CDN / proxy
Server Location
Hidden behind Cloudflare

Other sites using the same Cloudflare IP 104.18.39.173

How fast does api.storage load?

The average loading time of api.storage is 2100 ms. The Desktop speed index is 99 and mobile speed index is 99.

99
Good
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
2100 ms

Over the last 30 days, the field data shows that this page has a 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.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow

All pages served from this origin have an 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.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Largest Contentful Paint0.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
First Contentful Paint0.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
CSS Selector costs
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
Long critical network tree
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
Time to Interactive0.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
Font display
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Speed Index1.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
Total Blocking Time0 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
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Max Potential First Input Delay20 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
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
Does not have 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
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
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
99
Good
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
2100 ms

Over the last 30 days, the field data shows that this page has a 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.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow

All pages served from this origin have an 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.

CLSCumulative Layout Shift
0
0% fast0% avg0% slow
TTFBTime To First Byte
0
0% fast0% avg0% slow
FCPFirst Contentful Paint
0
0% fast0% avg0% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
0
0% fast0% avg0% slow
LCPLargest Contentful Paint
0
0% fast0% avg0% slow
Minimize third-party usage
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact
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
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint0.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
Third parties
Third party code can significantly impact load performance. to prioritize your page's content. Reduce and defer loading of third party code
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
Max Potential First Input Delay20 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
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Time to Interactive0.8 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
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Total Blocking Time0 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
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
CSS Selector costs
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
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
Long critical network tree
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
First Contentful Paint0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Font display
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Does not have 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 Index3.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does api.storage 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 api.storage are reduced by 58%.

58%
Reduced
Original
1.2 KB
Compressed
512 B

Saved 721 B off the original size

api.storage use br compression.

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

WOT 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 browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. api.storage supports HTTPS.

api.storage supports HTTPS
Verifying SSL Support. Please wait...
Common Name: api.storage
Organization:
Location:
Issuer: WE1
Valid from: Apr 1 11:44:07 2025 GMT
Valid until: Jun 30 12:43:44 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 & HTTP/3 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. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.

api.storage supports HTTP/2
api.storage supports HTTP/3
Verifying HTTP/2 and HTTP/3 Support. Please wait...
Details

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.

HTTP/1.1
date: Thu, 03 Apr 2025 12:34:45 GMT
content-type: text/html
x-powered-by: ASP.NET
via: 1.1 google
alt-svc: h3=":443"; ma=86400
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=ixTwR4L9VIlTSBhrZUOIO_AP95s3HhUXet70Om4IRyk-1743683685-1.0.1.1-8wQrmW.E.Sno8_0RpwRYf4gli3GemvFCP1uQIzieN6UXkbB1chlU9RshONL3Ono2nFtP5wYJqLmze.Jsy86M3Guhzamj1TsLc47MVPQrPXE; path=/; expires=Thu, 03-Apr-25 13:04:45 GMT; domain=.api.storage; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 92a89a0b886f4417-ORD
content-encoding: br

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.

TypeIPTarget / TXTTTL
A 172.64.148.83 20
A 104.18.39.173 20
NS derek.ns.cloudflare.com 3320
NS abby.ns.cloudflare.com 3320
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 September 30, 2022 and will expire on September 30, 2025 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 December 20, 2024.

Domain Created
2022-09-30
Domain Expires
2025-09-30
Domain Updated
2024-12-20
Domain Age
4 years 1 months 4 days
Domain Registrar
Go Daddy, LLC
Domain Owner
Domains By Proxy, LLC
WHOIS
Domain Name: API.STORAGE
Registry Domain ID: D325526650-CNIC
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com/
Updated Date: 2024-12-20T15:13:26.0Z
Creation Date: 2022-09-30T20:34:34.0Z
Registry Expiry Date: 2025-09-30T23:59:59.0Z
Registrar: Go Daddy, LLC
Registrar IANA ID: 146
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Registrant Organization: Domains By Proxy, LLC
Registrant State/Province: Arizona
Registrant Country: US
Registrant 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.
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.
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: ABBY.NS.CLOUDFLARE.COM
Name Server: DEREK.NS.CLOUDFLARE.COM
DNSSEC: unsigned
Billing 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.
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.4805058800
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2025-04-03T12:35:21.0Z > IMPORTANT INFORMATION ABOUT THE DEPLOYMENT OF RDAP: please visit
https://www.centralnicregistry.com/support/information/rdap 
More on HypeStat
Activity

Recently Analyzed Sites

elio-aios.fr
HTTP/2 supportedHTTPS supported 39 secs
wibbbb4141.com
HTTP/3 supportedHTTPS supported 42 secs
whtianlv.com
HTTP/3 supportedHTTPS supported 59 secs
hypebeast.com
HTTP/3 supportedHTTPS supported 1 min
wiaps.com
HTTP/3 supportedHTTPS supported 1 min
esoterica.de
HTTP/2 supportedHTTPS supported 2 mins
veritask.ai
HTTP/3 supportedHTTPS supported 2 mins
asyabahis1274.com
HTTP/2 not supportedHTTPS supported 2 mins
cianitas.com.br
HTTP/2 supportedHTTPS supported 3 mins
asvezestembage.com.br
HTTP/2 supportedHTTPS supported 3 mins
bigbets.tech
HTTP/2 supportedHTTPS supported 4 mins
asyoukorea.com
HTTP/2 supportedHTTPS supported 4 mins
good111.fans
HTTP/2 supportedHTTPS supported 5 mins
golive-asia.com
HTTP/2 supportedHTTPS supported 5 mins
golperdiary.com
HTTP/2 supportedHTTPS supported 5 mins

Latest Viewed Sites

academiaexpertia.com
3 secs
sontogel888.com
3 secs
***indo13.com
3 secs
789bet4.com
4 secs
***.com
4 secs
rulewap.tk
4 secs
tiaokan.fun
5 secs
***.com
5 secs
rosstip.ru
6 secs
yiyibox.com
6 secs
turbozonebd.com
7 secs
***.br
8 secs
upwar-bauro.sbs
9 secs
totalads.in
10 secs
story.bluesystem.org
12 secs
Resources

Custom Widget

api.storage
Daily Visitors 3
Monthly Visits 90.9
Pages / Visit 1.00
HypeRank #2,883,044
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Own this website?

Verify that you own api.storage to hide WHOIS data or traffic estimates, write the site description, connect Google Analytics to show your real traffic, or remove the report from HypeStat.
Manage this site →