Krugozor.wedding

krugozor.wedding Profile

What technologies does krugozor.wedding use?

These are the technologies used at krugozor.wedding. krugozor.wedding has a total of 1 technologies installed in 2 different categories.

Web Servers 1

Nginx

Reverse proxies 1

Nginx

krugozor.wedding Traffic Analysis

Krugozor.wedding is ranked #16,609,434 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

16,609,434

*All traffic values are estimates only.

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to krugozor.wedding, per platform.

Where is krugozor.wedding hosted?

Krugozor.wedding 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 185.43.6.152

Does krugozor.wedding 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 krugozor.wedding are reduced by 73%.

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. krugozor.wedding does not support 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.

Date: Mon, 02 Mar 2020 16:13:02 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
Set-Cookie: __cfduid=dce136e36a75438bbf1edad5b63b3d9e61583165582; expires=Wed, 01-Apr-20 16:13:02 GMT; path=/; domain=.9daysfx.com; HttpOnly; SameSite=Lax
Location: https://9daysfx.com/
X-Turbo-Charged-By: LiteSpeed
CF-Cache-Status: DYNAMIC
Server: cloudflare
CF-RAY: 56dc67199ef0c81a-DFW

HTTP/2 200 
date: Mon, 02 Mar 2020 16:13:03 GMT
content-type: text/html
set-cookie: __cfduid=d6a87f552d4c37220940103fb45cd7b1a1583165583; expires=Wed, 01-Apr-20 16:13:03 GMT; path=/; domain=.9daysfx.com; HttpOnly; SameSite=Lax
last-modified: Sat, 18 May 2019 14:05:36 GMT
vary: Accept-Encoding
x-turbo-charged-by: LiteSpeed
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
server: cloudflare
cf-ray: 56dc671faf29c7ee-DFW
content-encoding: br
Date: Mon, 02 Mar 2020 16:13:24 GMT
Server: nginx/1.17.6
Content-Type: text/html; charset=UTF-8
Content-Length: 0
Pragma: no-cache
X-Pingback: http://amazingworldcare.com/xmlrpc.php
X-Redirect-By: WordPress
Expires: Wed, 11 Jan 1984 05:00:00 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Location: https://amazingworldcare.com/
host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ==
X-Endurance-Cache-Level: 2
X-Server-Cache: true
X-Proxy-Cache: MISS
Set-Cookie: PHPSESSID=484e52bfe6c2cea70c53e416b7a879c1; path=/

HTTP/2 200 
date: Mon, 02 Mar 2020 16:13:26 GMT
server: nginx/1.17.6
content-type: text/html; charset=UTF-8
expires: Thu, 19 Nov 1981 08:52:00 GMT
cache-control: no-store, no-cache, must-revalidate
pragma: no-cache
x-pingback: https://amazingworldcare.com/xmlrpc.php
link: <https://amazingworldcare.com/wp-json/>; rel="https://api.w.org/", <https://amazingworldcare.com/>; rel=shortlink
vary: Accept-Encoding
content-encoding: gzip
host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ==
x-endurance-cache-level: 2
x-server-cache: true
x-proxy-cache: MISS
set-cookie: PHPSESSID=102053a62f2822857981a26af372bd81; path=/
Date: Mon, 02 Mar 2020 16:13:30 GMT
Content-Type: text/html;charset=utf-8
Connection: keep-alive
x-seen-by: gv/XVF9HsGpk8A2KWukUzOwfbs+7qUVAqsIx00yI78k=,BTzakfJUbU/4CBguyutVd1BmDjYppDd6MXvikk+MVGE=,1wy2ILu/S4rlWT/R4rqCrak2rkv0vJrEwG04nSYjamo=,qJS91GsscGZlb16v+8nwmF3+thlwCBmLRiR1yQ0igkMPUN6zYCeYUhP+LoeE7OiY,WSO+u2BWDrxZld83W5N69vLZL6/0VyFIyzg3OqXL+1fmAB1KkckSK1DWtKj7c2HygavG7/btK3d2+RPXdqSxwg==
cache-control: no-cache
content-language: en
Content-Encoding: gzip
X-Wix-Request-Id: 1583165610.45126540233570114274
Transfer-Encoding: chunked
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Expires: -1
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Mon, 02 Mar 2020 16:13:30 GMT
Content-Length: 485
Age: 1
Connection: keep-alive
Server: nginx/1.14.1
Date: Mon, 02 Mar 2020 16:13:32 GMT
Content-Type: text/html
Content-Length: 185
Connection: keep-alive
Location: https://krugozor.wedding/

HTTP/1.1 200 OK
Server: nginx/1.14.1
Date: Mon, 02 Mar 2020 16:13:32 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 8314
Last-Modified: Mon, 02 Mar 2020 10:45:18 GMT
Connection: keep-alive
ETag: "5e5ce3be-207a"
Content-Encoding: gzip
Cache-Control: private, max-age=0

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.