dyne.github.io Dyne.github.io

   
Digital Community and Free Software Foundry

Domain Summary

What IP addresses does Dyne.github.io resolve to?

• Dyne.github.io resolves to the IP addresses 2606:50c0:8000::153, 185.199.110.153.

Where are Dyne.github.io servers located in?

• Dyne.github.io has servers located in California, United States.

dyne.github.io Profile

Title:Digital Community and Free Software Foundry Description:🚀 Empowering artists, creatives and citizens for more than 20 years.
Edit Site Info

What technologies does dyne.github.io use?

These are the technologies used at dyne.github.io. dyne.github.io has a total of 6 technologies installed in 5 different categories.
CDN
Fastly Fastly
jsDelivr jsDelivr
PaaS
GitHub Pages GitHub Pages
Miscellaneous
Open Graph Open Graph
JavaScript Libraries
Swiper Swiper
Caching
Varnish Varnish

dyne.github.io Traffic Analysis

There's no enough data about dyne.github.io traffic.
Daily Visitors n/a
Monthly Visits n/a
Pages per Visit n/a
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
 n/a
Monthly Visits:
n/a
Pages per Visit:
n/a
Daily Pageviews:
n/a
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
 n/a
HypeRank:
n/a
*All traffic values are estimates only.
Last update was 5 hours ago
     
This can take up to 60 seconds. Please wait...

Update will be available in 19 hours
*HypeStat.com is not promoting or affiliated with dyne.github.io in any way. Only publicly available statistics data are displayed.

  ▼

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:
  dyne.github.io
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Ad Experience Report ▼

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

Mobile summary

Root domain:
dyne.github.io
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:
dyne.github.io
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:
dyne.github.io
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 dyne.github.io hosted? ▼

Dyne.github.io may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2606:50c0:8000::153, 185.199.110.153
ASN:
AS54113 
ISP:
Fastly 
Server Location:
California, CA
United States, US
 

Other sites hosted on 185.199.110.153

How fast does dyne.github.io load? ▼

The average loading time of dyne.github.io is 170 ms. The Desktop speed index is 0 and mobile speed index is 66.
Average Load Time:
170 ms

Page Speed (Google PageSpeed Insights) - Mobile

66
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST 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)0ms 0% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)703ms 0% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 80% 15% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 15% 4% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)967ms 0% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 91% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
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)1.1s 0% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 93% 4% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 4% 1% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 1%

Origin Data

All pages served from this origin have an FAST 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)0ms 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)703ms 80% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 80% 15% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 15% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)967ms 91% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 91% 4% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 4% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
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)1.1s 93% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 93% 4% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 4% 1% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 1%

Lab Data

Speed Index 5.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Max Potential First Input Delay 80 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
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint 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
Time to Interactive 25.5 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
Largest Contentful Paint 24.9 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
Total Blocking Time 30 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 3.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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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
Legacy JavaScript  
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support older browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
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

Does dyne.github.io 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 dyne.github.io are reduced by 63%.
dyne.github.io use gzip compression.
Original size: 208.29 KB
Compressed size: 75.74 KB
File reduced by: 132.56 KB (63%)

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. dyne.github.io supports HTTPS.
 dyne.github.io supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: dyne.org
Organization:
Location:
Issuer: R11
Valid from: May 5 08:10:10 2025 GMT
Valid until: Aug 3 08:10:09 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R11
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 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.
 dyne.github.io 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: GitHub.com
content-type: text/html
location: https://dyne.org/
x-github-request-id: D8B8:1C62C0:2D8DE6:2DE70F:68503FA9
accept-ranges: bytes
age: 0
date: Mon, 16 Jun 2025 16:00:41 GMT
via: 1.1 varnish
x-served-by: cache-fra-eddf8230054-FRA
x-cache: MISS
x-cache-hits: 0
x-timer: S1750089642.669874,VS0,VE102
vary: Accept-Encoding
x-fastly-request-id: 8c06a2915fe84bc5ff68a91a1281873bf60265cd
content-length: 162

HTTP/2 200 
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Fri, 02 May 2025 09:44:01 GMT
access-control-allow-origin: *
etag: W/"681493e1-3412d"
expires: Tue, 10 Jun 2025 03:31:27 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: F782:1CA539:F956D2:FBB29E:6847A4B6
accept-ranges: bytes
age: 490
date: Mon, 16 Jun 2025 16:00:41 GMT
via: 1.1 varnish
x-served-by: cache-fra-eddf8230114-FRA
x-cache: HIT
x-cache-hits: 0
x-timer: S1750089642.802864,VS0,VE4
vary: Accept-Encoding
x-fastly-request-id: 59da456c77f4d4476907a39364c00ca34e073c09
content-length: 77553

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
A 185.199.110.153 3114
A 185.199.111.153 3114
A 185.199.108.153 3114
A 185.199.109.153 3114
AAAA 2606:50c0:8002::153 1914
AAAA 2606:50c0:8003::153 1914
AAAA 2606:50c0:8001::153 1914
AAAA 2606:50c0:8000::153 1914

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.
WhoIs:
 

Malformed request.
>>> Last update of WHOIS database: 2025-06-16T16:01:52Z