Fairylei.yokohama

fairylei.yokohama Profile

What technologies does fairylei.yokohama use?

These are the technologies used at fairylei.yokohama. fairylei.yokohama has a total of 4 technologies installed in 4 different categories.

Font Scripts 2

Font Awesome Google Font API

Web Servers 1

Nginx

Reverse proxies 1

Nginx

JavaScript Libraries 1

jQuery

fairylei.yokohama Traffic Analysis

Fairylei.yokohama is ranked #21,367,657 in the world.

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

21,367,657

*All traffic values are estimates only.

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to fairylei.yokohama, per platform.

Where is fairylei.yokohama hosted?

Fairylei.yokohama may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

Other sites hosted on 133.130.35.22

Does fairylei.yokohama 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 fairylei.yokohama are reduced by 72%.

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.

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. fairylei.yokohama supports HTTPS.

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.

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
Date: Sun, 21 Aug 2022 16:49:05 GMT
Content-Type: text/html;charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
Content-Encoding: gzip
server: nginx
date: Sun, 21 Aug 2022 16:49:07 GMT
content-type: text/html; charset=utf-8
content-length: 0
location: http://fairylei.yokohama/
set-cookie: PHPSESSID=r2r9ka44nlhuikp16dhimq1gfc; path=/; HttpOnly
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
x-xss-protection: 1; mode=block
set-cookie: uid=CvEFC2MCYgMzGlSIDVCUAg==; expires=Thu, 31-Dec-37 23:55:55 GMT; path=/
p3p: policyref="/w3c/p3p.xml", CP="CUR ADM OUR NOR STA NID"

HTTP/1.1 200 OK
Server: nginx
Date: Sun, 21 Aug 2022 16:49:07 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 5345
Set-Cookie: PHPSESSID=haiql0aakqv3djee72idvk1smv; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
X-XSS-Protection: 1; mode=block
Vary: Accept-Encoding
Content-Encoding: gzip
Set-Cookie: uid=CvEFCGMCYgNQ9lOCLrnTAg==; expires=Thu, 31-Dec-37 23:55:55 GMT; path=/
P3P: policyref="/w3c/p3p.xml", CP="CUR ADM OUR NOR STA NID"

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.