memory.lol Memory.lol

   
GitHub - travisbrown/memory.lol: memory.lol

Domain Summary

What is the traffic rank for Memory.lol?

• Memory.lol ranks #2,405,320 globally on HypeStat.

What percent of global Internet users visit Memory.lol?

9.6E-6% of global Internet users visit Memory.lol

How many people visit Memory.lol each day?

• Memory.lol receives approximately 474 visitors and 2,750 page impressions per day.

How much Memory.lol can earn?

• Memory.lol should earn about $11.22/day from advertising revenue.

What is Memory.lol estimated value?

• Estimated value of Memory.lol is $10,142.77.

What IP addresses does Memory.lol resolve to?

• Memory.lol resolves to the IP addresses 54.219.233.211.

Where are Memory.lol servers located in?

• Memory.lol has servers located in San Jose, California, 95141, United States.

memory.lol Profile

Title:GitHub - travisbrown/memory.lol: memory.lol Description:memory.lol. Contribute to travisbrown/memory.lol development by creating an account on GitHub.
Category:Computers Electronics and Technology / Social Media Networks

What technologies does memory.lol use?

These are the technologies used at memory.lol. memory.lol has a total of 6 technologies installed in 3 different categories.

memory.lol Traffic Analysis

Memory.lol is ranked #2,405,320 in the world. This website is viewed by an estimated 474 visitors daily, generating a total of 2.8K pageviews. This equates to about 14.4K monthly visitors. Memory.lol traffic has decreased by 91.93% compared to last month.
Daily Visitors474
93.74%
Monthly Visits14.4K
91.93%
Pages per Visit5.80
48.82%
Visit duration01:22
19.05%
Bounce Rate60.57%
218.21%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
474
Monthly Visits:
14,362
Pages per Visit:
5.80
Daily Pageviews:
2,750
Avg. visit duration:
01:22
Bounce rate:
60.57%
Global Reach:
9.6E-6%
Monthly Visits (SEMrush):
1,073
Monthly Unique Visitors (SEMrush):
635
Monthly Visits (SimilarWeb):
13,940
HypeRank:
2,405,320
SEMrush Rank:
17,699,276
SimilarWeb Rank:
1,960,606
*All traffic values are estimates only.

Traffic sources

Direct:
60.11%
Referral:
0%
Search:
0%
Social:
39.89%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

4.2K
JUN
178K
JUL
14.4K
AUG

Which sites are competitors to memory.lol?

Websites similar to memory.lol 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.
Last update was 640 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with memory.lol 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:
2
Bing Index:
4

 

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:
  memory.lol
Rank:
(Rank based on keywords, cost and organic traffic)
  17,699,276
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1
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

Revenue report

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

How much would memory.lol make?

Daily Revenue:
$11.22
Monthly Revenue:
$336.60
Yearly Revenue:
$4,095.30
*All earnings values are estimates only.

How much is memory.lol worth?

Website Value:
$10.1K

Ad Experience Report

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

Mobile summary

Root domain:
memory.lol
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:
memory.lol
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:
memory.lol
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 memory.lol hosted?

Memory.lol may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
54.219.233.211
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
San Jose
California, CA
95141
United States, US
 

Other sites hosted on 54.219.233.211

There are no other sites hosted on this IP

How fast does memory.lol load?

The average loading time of memory.lol is 635 ms. The Desktop speed index is 87 and mobile speed index is 61.
Average Load Time:
635 ms

Page Speed (Google PageSpeed Insights) - Desktop

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

Cumulative Layout Shift (CLS)6ms 84% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 84% 10% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 10% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.0s 57% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 57% 37% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 37% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.4s 87% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 87% 9% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 9% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)3ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)68ms 94% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 94% 3% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 3% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.6s 91% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 91% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 3% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 3%

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.

Cumulative Layout Shift (CLS)6ms 84% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 84% 10% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 10% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.0s 57% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 57% 37% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 37% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.4s 87% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 87% 9% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 9% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)3ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 98% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)68ms 94% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 94% 3% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 3% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)1.6s 91% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 91% 5% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 5% 3% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 3%

Lab Data

Largest Contentful Paint 1.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest 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 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
Time to Interactive 1.7 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
First Contentful Paint 1.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
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
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
First Meaningful Paint 1.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 140 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
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 50 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

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.

Cumulative Layout Shift (CLS)2ms 84% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 84% 10% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 10% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.0s 57% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 61% 32% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 32% 6% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.9s 87% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 72% 17% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 17% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)18ms 94% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 3% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%
Interactive To Next Paint (INP)273ms 94% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 65% 24% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 24% 10% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 10%
Largest Contentful Paint (LCP)2.3s 91% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 78% 13% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 13% 7% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 7%

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.

Cumulative Layout Shift (CLS)2ms 84% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 84% 10% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 10% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.0s 61% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 61% 32% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 32% 6% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 6%
First Contentful Paint (FCP)1.9s 72% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 72% 17% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 17% 9% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 9%
First Input Delay (FID)18ms 98% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 3% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%
Interactive To Next Paint (INP)273ms 65% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 65% 24% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 24% 10% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 10%
Largest Contentful Paint (LCP)2.3s 78% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 78% 13% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 13% 7% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 7%

Lab Data

Speed Index 4.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Preconnect to required origins  
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
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
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 410 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
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
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
Total Blocking Time 520 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
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
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
Time to Interactive 6.9 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
First Meaningful Paint 3.7 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 3.7 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

Does memory.lol 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 memory.lol are reduced by 81%.
memory.lol use gzip compression.
Original size: 261.18 KB
Compressed size: 48.29 KB
File reduced by: 212.89 KB (81%)

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. memory.lol supports HTTPS.
 memory.lol supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: github.com
Organization: "GitHub, Inc."
Location: San Francisco, California, US
Issuer: DigiCert TLS Hybrid ECC SHA384 2020 CA1
Valid from: Feb 14 00:00:00 2023 GMT
Valid until: Mar 14 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize:
Common Name: DigiCert TLS Hybrid ECC SHA384 2020 CA1
Organization: DigiCert Inc
Location: US
Issuer: DigiCert Global Root CA
Valid from: Apr 14 00:00:00 2021 GMT
Valid until: Apr 13 23:59:59 2031 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.
 memory.lol 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: nginx/1.22.1
date: Sat, 16 Sep 2023 01:42:02 GMT
content-type: text/html
content-length: 145
location: https://github.com/travisbrown/memory.lol/

HTTP/2 200 
server: GitHub.com
date: Sat, 16 Sep 2023 01:42:02 GMT
content-type: text/html; charset=utf-8
vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
etag: W/"f2e226a6e0e197d337cc9aa775305b24"
cache-control: max-age=0, private, must-revalidate
strict-transport-security: max-age=31536000; includeSubdomains; preload
x-frame-options: deny
x-content-type-options: nosniff
x-xss-protection: 0
referrer-policy: no-referrer-when-downgrade
content-security-policy: default-src 'none'; base-uri 'self'; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src 'self' uploads.github.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events objects-origin.githubusercontent.com *.actions.githubusercontent.com productionresultssa0.blob.core.windows.net/ productionresultssa1.blob.core.windows.net/ productionresultssa2.blob.core.windows.net/ productionresultssa3.blob.core.windows.net/ productionresultssa4.blob.core.windows.net/ productionresultssa5.blob.core.windows.net/ productionresultssa6.blob.core.windows.net/ productionresultssa7.blob.core.windows.net/ productionresultssa8.blob.core.windows.net/ productionresultssa9.blob.core.windows.net/ wss://*.actions.githubusercontent.com github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action 'self' github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors 'none'; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com support.github.com; img-src 'self' data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com secured-user-images.githubusercontent.com/ user-images.githubusercontent.com/ private-user-images.githubusercontent.com opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com objects-origin.githubusercontent.com *.githubusercontent.com; manifest-src 'self'; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/ private-user-images.githubusercontent.com; script-src github.githubassets.com; style-src 'unsafe-inline' github.githubassets.com; upgrade-insecure-requests; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
content-encoding: gzip
set-cookie: _gh_sess=pX%2B4sSZ4NVZDSfU0%2BJ2V3HvPG8TFoezWpZ4Up1nVxRzVPN5jR9RUm%2FAzIsMwmNCphoDW7ZQYf%2BPxLLrfWP0Ihv%2Ftef2D94j9OFlpq65RWfyJ%2FjqNt1nEr8PBwsvCqK29eet4WS%2BPU0YkvyRhetNdnNHv90YFLpoYqOT5EtYJJQkENW%2F8%2F9nTpsCpNGZxcSruiELVv3XgQ0wiFQ8o0Yb0SH7SnNPXLMelBglawSZUCqpMmpHlRcfyK%2FKfKYVUMkmen9bv0QPIdyKruXiIN%2BC1wg%3D%3D--mo9ojnBDTsjpW5wJ--x63pMAzSQ4YMiv1vkyDjUQ%3D%3D; Path=/; HttpOnly; Secure; SameSite=Lax
set-cookie: _octo=GH1.1.925163815.1694828522; Path=/; Domain=github.com; Expires=Mon, 16 Sep 2024 01:42:02 GMT; Secure; SameSite=Lax
set-cookie: logged_in=no; Path=/; Domain=github.com; Expires=Mon, 16 Sep 2024 01:42:02 GMT; HttpOnly; Secure; SameSite=Lax
accept-ranges: bytes
x-github-request-id: 8ACC:7B7B:267F1:32A0B:650507EA

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
A 54.219.233.211 1717
NS dns2.registrar-servers.com 3518
NS dns1.registrar-servers.com 3518

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:
 

Domain Name: memory.lol

>>> This name is not available for registration:

>>> This TLD has been transitioned to CentralNIC

>>> Last update of WHOIS database: 2023-09-16T01:43:23.134Z