dweb.link was accessible in Finland

GET https://about.ipfs.io
Accept-Ranges:
bytes
Access-Control-Allow-Origin:
*
Age:
34535
Cache-Control:
public, max-age=0, must-revalidate
Content-Disposition:
inline
Content-Length:
16198
Content-Type:
text/html; charset=utf-8
Date:
Sun, 10 Aug 2025 22:50:00 GMT
Etag:
"6696b8047ce7c44e787e6d658ced2ad5"
Last-Modified:
Sun, 10 Aug 2025 08:23:51 GMT
Server:
Vercel
Strict-Transport-Security:
max-age=63072000
X-Vercel-Cache:
HIT
X-Vercel-Id:
arn1::rxc8z-1754866200192-397ce6eaba6b
<!DOCTYPE HTML>

<html>

	<head>
	<meta name="generator" content="Hugo 0.124.0">
	<title>About the IPFS.io Public Gateway</title>
	<meta charset="utf-8" />
	<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
	<meta name="description" content="IPFS.io Public Gateway - Free public service to access IPFS content through your web browser. Bridge between HTTP and decentralized IPFS protocol without installing software.">
	<meta name="author" content="IPFS Foundation">
	<meta name="keywords" content="IPFS, gateway, decentralized web, content addressing, dweb">

	<link rel="canonical" href="https://about.ipfs.io/">

	<meta property="og:title" content="About the IPFS.io Public Gateway">
	<meta property="og:description" content="IPFS.io Public Gateway - Free public service to access IPFS content through your web browser. Bridge between HTTP and decentralized IPFS protocol without installing software.">
	<meta property="og:image" content="https://about.ipfs.io/images/OIG.FZAB.jpeg">
	<meta property="og:url" content="https://about.ipfs.io/">
	<meta property="og:type" content="website">
	<meta property="og:site_name" content="IPFS.io Gateway">

	<meta name="twitter:card" content="summary_large_image">
	<meta name="twitter:title" content="About the IPFS.io Public Gateway">
	<meta name="twitter:description" content="IPFS.io Public Gateway - Free public service to access IPFS content through your web browser. Bridge between HTTP and decentralized IPFS protocol without installing software.">
	<meta name="twitter:image" content="https://about.ipfs.io/images/OIG.FZAB.jpeg">
	<meta name="twitter:site" content="@IPFS">

	<meta name="msapplication-TileColor" content="#da532c">
    <meta name="theme-color" content="#ffffff">	
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
    <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
    <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
    <link rel="manifest" href="/site.webmanifest">
    <link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5">

	<link rel="stylesheet" href="/css/main.min.css">

	<noscript><link rel="stylesheet" href="/css/noscript.min.css" /></noscript>

</head>

	<body class="is-preload">

		<div id="wrapper" class="divided">

<section class="wrapper style2 align-center" id="disclaimer">
    <div class="inner">
        <div class="content"><div class="disclaimer-notice">
  <p><strong>Looking for the IPFS Project?</strong> This is the ipfs.<u>io</u> public gateway. The IPFS Project website is at <a href="https://ipfs.tech" target="_blank">ipfs.<u>tech</u></a></p>
</div>
</div>

        <ul class="actions">

            <li><a href="#start" class="button primary">About ipfs.<u>io</u> Gateway</a></li>

            <li><a href="#reporting-abuse" class="button">Report Abuse</a></li>

            <li><a href="https://ipfs.tech" class="button" target="_blank">Go to ipfs.<u>tech</u></a></li>

        </ul>

    </div>
</section>

<section class="banner style1 orient-left content-align-left image-position-right fullscreen onload-image-fade-in onload-content-fade-right" id="start">
    <div class="content">
        <h1>IPFS.<u>io</u> Public Gateway</h1>
        <p class="major">A Public Good for Accessing the Decentralized Web
</p>
        <p>We are enabling users like you to navigate through the decentralized web with unparalleled speed and security. As a conduit between the traditional web and the decentralized IPFS web, our gateway ensures that your journey through the boundless universe of decentralized data is not only seamless but also reliable and robust.
</p>
        <ul class="actions stacked">
            <li><a href="#public-utility" class="button primary large wide smooth-scroll-middle">Get Started</a></li>
        </ul>
    </div>
    <div class="image">
        <img src="images/OIG.FZAB.jpeg" alt="IPFS Gateway illustration showing decentralized web connectivity" />
    </div>
</section>

<section class="spotlight style1 orient-right content-align-left image-position-center onscroll-image-fade-in" id="public-utility">
    <div class="content">
        <h2>Public Utility</h2>
        <p>An IPFS gateway acts as a bridge between the traditional web protocol (HTTP) and the IPFS protocol.
It listens for requests for IPFS content, retrieves that content via IPFS, and makes it available via HTTP.
This allows anyone to access content from public IPFS networks, no matter what web browser they're using.

The IPFS.io public gateway is provided for free on an as-is basis, and not intended to be part of your
critical path or production infrastructure. The features it supports are listed <a href="https://docs.ipfs.tech/concepts/public-utilities/#supported-features" target="_blank">on the docs website</a>.
It is one of several <a href="https://ipfs.github.io/public-gateway-checker/" target="_blank">public IPFS gateways</a>.
</p>
        <ul class="actions stacked">
            <li><a href="#acceptable-use" class="button">Learn More</a></li>
        </ul>
    </div>
    <div class="image">
        <img src="images/OIG.fuGq.jpeg" alt="" />
    </div>
</section>

<section class="spotlight style1 orient-left content-align-left image-position-center onscroll-image-fade-in" id="acceptable-use">
    <div class="content">
        <h2>Acceptable Use Policy</h2>
        <p>The IPFS.io public gateway allows people to access a wide variety of data, content, and materials (referred to as “Content”) uploaded to the IPFS network by third-parties. Please note that you will be solely responsible for the consequences of using, disclosing, storing, transferring, or transmitting this Content. 

Any Content violating this Acceptable Use policy that is served through the IPFS.io public gateway may be immediately removed or disabled without any
compensation to you, such as by adding that Content's identifier to the <a href="https://badbits.dwebops.pub/" target="_blank">Bad Bits denylist</a>.

The following types of Content violate the Acceptable Use policy: 
<ul>
  <li>scams, spam, and server misuse (such as viruses, phishing/spoofing content, or spam);</li>
  <li>content infringing on the intellectual property, privacy, or publicity rights of others;</li>
  <li>unlawful obscene content; content soliciting unlawful services; child sexual abuse material or terrorist content; or</li>
  <li>content reasonably likely to cause or increase the risk of harm to any people/groups.</li>
</ul>
</p>
        <ul class="actions stacked">
            <li><a href="#reporting-abuse" class="button">Learn More</a></li>
        </ul>
    </div>
    <div class="image">
        <img src="images/OIG.p4NG.jpeg" alt="" />
    </div>
</section>

<section class="spotlight style1 orient-right content-align-left image-position-center onscroll-image-fade-in" id="reporting-abuse">
    <div class="content">
        <h2>Reporting Abuse</h2>
        <p><p><strong>To report abuse or submit a takedown request on <u>ipfs.io</u> or <u>dweb.link</u> gateways, email <a href="mailto:abuse@ipfs.io" target="_blank">abuse@ipfs.io</a>.</strong></p>

Your email should include the relevant CID or URL,
and the reason for your report or request. For copyright-related requests, please include all of
<a href="https://copyrightalliance.org/education/copyright-law-explained/the-digital-millennium-copyright-act-dmca/write-dmca-takedown-notice/" target="_blank">the required details for a DMCA takedown request.</a>

You will receive an automated system receipt. Next, someone from the takedown team will review the request to make sure it is legitimate and
determine appropriate next steps based on the Acceptable Use policy above.

If the takedown team decides to issue a takedown based on the Acceptable Use policy, the relevant information from the request will be added to the
denylist at <a href="https://badbits.dwebops.pub/" target="_blank">https://badbits.dwebops.pub/</a>. The gateways will return a 410 error when users try to fetch the content in question.

Your browser may have a local cache of the content in question and might not immediately reflect that something has been blocked on the gateways.
To avoid browser caching, switch to your browser's incognito or private mode. You can also prevent caching issues by using a command-line tool
such as cURL or wget.
</p>
        <ul class="actions stacked">
            <li><a href="#faqs" class="button">Learn More</a></li>
        </ul>
    </div>
    <div class="image">
        <img src="images/OIG.8bG8.jpeg" alt="" />
    </div>
</section>

<section class="wrapper style1 style1 medium onscroll-fade-in" id="faqs">
    <div class="inner">
        <h2>Frequently Asked Questions</h2>
        <p>Below you can find answers to the most frequently asked questions.
</p>
        <div class="content faqs">
            <dl>

<section>
    <dt>How do the ipfs.io/dweb.link gateways work?</dt>
    <dd>
        <p>The ipfs.io gateway runs <a href="https://github.com/ipfs/rainbow" target="_blank">Rainbow</a>,
an implementation of the <a href="https://specs.ipfs.tech/http-gateways" target="_blank">IPFS HTTP Gateway API</a>,
to find, retrieve, and serve data. It listens for requests for IPFS content, retrieves
that content via IPFS, and makes it available to the requester via HTTP. Read the IPFS docs
to learn more about <a href="https://docs.ipfs.tech/concepts/ipfs-gateway/" target="_blank">IPFS Gateways</a>
or other <a href="https://docs.ipfs.tech/concepts/public-utilities/#public-ipfs-gateways" target="_blank">Public IPFS Utilities</a>.     
</p>
    </dd>
</section>

<section>
    <dt>Why am I getting a full response instead of streaming a large video or using an HTTP Range request?</dt>
    <dd>
        <p>HTTP Range requests are limited to files up to 5GiB due to Cloudflare CDN restrictions. For files larger than this, you'll receive a standard HTTP 200 response instead.
</p>
    </dd>
</section>

<section>
    <dt>I&#39;m trying to use the gateway but something else is not working, who should I talk to?</dt>
    <dd>
        <p>The best way to get support is to describe your issue clearly and in sufficient detail on the
<a href="https://discuss.ipfs.tech/" target="_blank">IPFS Forum</a>.     
</p>
    </dd>
</section>

<section>
    <dt>How are these gateways funded? Who is behind this?</dt>
    <dd>
        <p>The ipfs.io/dweb.link public gateways are maintained by <a href="https://ipshipyard.com/" target="_blank">Interplanetary Shipyard</a>
on behalf of the IPFS Foundation. The funds are contributed by a range of donors
who wish to support digital public infrastructure.
<a href="mailto:info@ipfs.io" target="_blank">Join them, all contributions are welcome!</a>
</p>
    </dd>
</section>

<section>
    <dt>What&#39;s the relationship between gateways and other IPFS instances?</dt>
    <dd>
        <p><a href="https://docs.ipfs.tech/install/">Running IPFS directly</a> is more efficient, but not all users are able to do it today.
Gateways are an interim solution. Longer term, the IPFS project aims to increase direct support for
ipfs:// in browsers and applications.
There will always be a role for gateways, but we anticipate that role will shrink as direct
IPFS support becomes more prevalent.
</p>
    </dd>
</section>

<section>
    <dt>How does the gateway ensure whether the data they return matches the Content ID (CID) in the request? Can I access the gateways in a trustless way?
</dt>
    <dd>
        <p>The ipfs.io gateway is one of the first that verifies the data against the requested CID before being
returned to users. We do however recommend that clients implement their own verification as that is a
foundational part of IPFS. To simplify this, gateways support
<a href="https://specs.ipfs.tech/http-gateways/trustless-gateway/#accept-request-header" target="_blank">trustless content types</a>
that enable <a href="https://docs.ipfs.tech/reference/http/gateway/#trustless-verifiable-retrieval" target="_blank">verifiable retrieval</a>.
This requires an explicit opt-in from the client at the time of the request.

If you are interested in exploring this more, we recommend you experiment with
<a href="https://inbrowser.link/" target="_blank">inbrowser.link</a>, a Service Worker gateway built with
<a href="https://helia.io/" target="_blank">Helia</a>, a JS IPFS implementation that supports trustless retrievals.
</p>
    </dd>
</section>

<section>
    <dt>How do I report abuse (phishing, illegal content, DMCA) on ipfs.io and dweb.link?</dt>
    <dd>
        <p>To report abuse or submit a takedown request, please see the <a href="#reporting-abuse">Reporting Abuse</a> section below for detailed instructions on how to contact us with your report.
</p>
    </dd>
</section>

<section>
    <dt>How do I report abuse (phishing, illegal content, DMCA) on other gateways?</dt>
    <dd>
        <p>Our takedown policy is only effective for removing content from the IPFS.<u>io</u> Gateway Service operated by the IPFS team (<u>ipfs.io</u> & <u>dweb.link</u>). While a properly-configured gateway running our open-source code will also take down anything we have actioned, we cannot guarantee that all other public gateways will be or remain properly configured. To report abuse on different domains, please contact <a href="https://whois.domaintools.com/" target="_blank">their respective owners</a>.
</p>
    </dd>
</section>

            </dl>
        </div>
        <ul class="actions stacked">
            <li><a href="#contact-us" class="button">Learn More</a></li>
        </ul>
    </div>
</section>

<section class="spotlight style1 orient-right content-align-left image-position-center onscroll-image-fade-in" id="contact-us">
    <div class="content">
        <h2>Contact Us</h2>
        <p>For abuse and DMCA related inquiries, please see the <a href="#reporting-abuse">Reporting Abuse</a> section above.

If you would like to run your own gateway, please see <a href="https://docs.ipfs.tech/how-to/gateway-best-practices/#self-hosting-a-gateway" target="_blank">Self Hosting a Gateway</a> in the IPFS Docs and get in touch with any questions.

The ipfs.io public gateway is maintained by Interplanetary Shipyard on behalf of the IPFS Foundation. You can reach us at <a href="https://filecoinproject.slack.com/archives/C0573QZRETS" target="_blank">#waterworks-community</a> on Filecoin Slack, on GitHub at <a href="https://github.com/ipshipyard/waterworks-community" target="_blank">ipshipyard/waterworks-community</a>, and on the IPFS discussion forums at <a href="https://discuss.ipfs.tech/" target="_blank">discuss.ipfs.tech</a>.
</p>
        <ul class="actions stacked">
            <li><a href="#start" class="button">Back to top</a></li>
        </ul>
    </div>
    <div class="image">
        <img src="images/OIG.l8jl.jpeg" alt="" />
    </div>
</section>

<footer class="wrapper style1 align-center">
    <div class="inner">
        <ul class="icons">
            <li><a target="_blank" href="https://github.com/ipshipyard" class="icon brands style2 fa-github"><span class="label">Github</span></a></li>
            <li><a target="_blank" href="https://x.com/ipshipyard" class="icon brands style2 fa-twitter"><span class="label">Twitter</span></a></li>

            <li><a target="_blank" href="https://www.linkedin.com/company/ipshipyard/" class="icon brands style2 fa-linkedin"><span class="label">LinkedIn</span></a></li>
            <li><a target="_blank" href="mailto:contact@ipshipyard.com" class="fav icon style2 fa-envelope"><span class="label">Email</span></a></li>
        </ul>
        <p>&copy; 2025 IPFS Foundation
</div>
</footer>

		</div>

<script src='/js/bundle.min.js'></script>

	</body>
</html>
GET https://dweb.link/
Alt-Svc:
h3=":443"; ma=86400
Cache-Control:
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Cf-Ray:
96d30cb629938d71-HEL
Content-Length:
143
Content-Type:
text/html
Date:
Sun, 10 Aug 2025 22:50:00 GMT
Expires:
Thu, 01 Jan 1970 00:00:01 GMT
Location:
https://about.ipfs.io
Server:
cloudflare
<html>
<head><title>302 Found</title></head>
<body>
<center><h1>302 Found</h1></center>
<hr><center>cloudflare</center>
</body>
</html>

Failures

DNS Queries

TCP Connections

HTTP Requests

URL

Response Headers

Response Body

URL

Response Headers

Response Body

Resolver

Raw Measurement Data

Raw Measurement Data

Failures

DNS Queries

TCP Connections

HTTP Requests

URL

Response Headers

Response Body

URL

Response Headers

Response Body

Resolver

Raw Measurement DataDownload JSONExpand All

Raw Measurement Data

Raw Measurement Data