fxurl.date Fxurl.date

   
YOURLS — Your Own URL Shortener | http://fxurl.date/

Domain Summary

What is the traffic rank for Fxurl.date?

• Fxurl.date ranks #1,240,654 globally on HypeStat.

What percent of global Internet users visit Fxurl.date?

0.00011% of global Internet users visit Fxurl.date

How many people visit Fxurl.date each day?

• Fxurl.date receives approximately 5.4K visitors and 7,592 page impressions per day.

Which countries does Fxurl.date receive most of its visitors from?

• Fxurl.date is mostly visited by people located in Switzerland.

How much Fxurl.date can earn?

• Fxurl.date should earn about $42.14/day from advertising revenue.

What is Fxurl.date estimated value?

• Estimated value of Fxurl.date is $38,567.08.

What IP addresses does Fxurl.date resolve to?

• Fxurl.date resolves to the IP addresses 138.128.174.10.

Where are Fxurl.date servers located in?

• Fxurl.date has servers located in Orlando, Florida, 32826, United States.

fxurl.date Profile

Title:YOURLS — Your Own URL Shortener | http://fxurl.date/

What technologies does fxurl.date use?

These are the technologies used at fxurl.date. fxurl.date has a total of 2 technologies installed in 2 different categories.

fxurl.date Traffic Analysis

Fxurl.date is ranked #1,240,654 in the world. This website is viewed by an estimated 5.4K visitors daily, generating a total of 7.6K pageviews. This equates to about 164.3K monthly visitors.
Daily Visitors5.4K
Monthly Visits164.3K
Pages per Visit1.40
Visit duration n/a
Bounce Rate n/a
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
5,423
Monthly Visits:
164,317
Pages per Visit:
1.40
Daily Pageviews:
7,592
Avg. visit duration:
n/a
Bounce rate:
n/a
Global Reach:
0.00011%
HypeRank:
1,240,654
*All traffic values are estimates only.

Visitors by country

Country
Users%
 
Switzerland 100.0%

Where do visitors go on fxurl.date?

 
Reach%Pageviews%PerUser
fxurl.date
100.00%100.00%1
Last update was 1551 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with fxurl.date 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:
  fxurl.date
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

Revenue report

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

How much would fxurl.date make?

Daily Revenue:
$42.14
Monthly Revenue:
$1,264.20
Yearly Revenue:
$15,381.10
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Switzerland 7,592$42.14

Loss of money due to Adblock?

Daily Revenue Loss:
$7.58
Monthly Revenue Loss:
$227.53
Yearly Revenue Loss:
$2,768.31
Daily Pageviews Blocked:
1,367
Monthly Pageviews Blocked:
40,997
Yearly Pageviews Blocked:
498,794

Daily revenue loss by country

 
CountryBlockedLost Money
 
Switzerland 1,367$7.58

How much is fxurl.date worth?

Website Value:
$38.6K

Ad Experience Report

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

Mobile summary

Root domain:
fxurl.date
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:
fxurl.date
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:
fxurl.date
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 fxurl.date hosted?

Fxurl.date may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
138.128.174.10
ASN:
AS33182 
ISP:
HostDime.com, Inc. 
Server Location:
Orlando
Florida, FL
32826
United States, US
 

Other sites hosted on 138.128.174.10

How fast does fxurl.date load?

The average loading time of fxurl.date is 2624 ms. The Desktop speed index is 99 and mobile speed index is 100.
Average Load Time:
2624 ms

Page Speed (Google PageSpeed Insights) - Desktop

99
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Origin Data

All pages served from this origin have an 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.

First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Lab Data

Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First CPU Idle 0.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First Contentful Paint 0.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more
First Meaningful Paint 0.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
Time to Interactive 0.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

100
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a 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.

First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Origin Data

All pages served from this origin have an 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.

First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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%

Lab Data

First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more
Time to Interactive 1.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
Minimize third-party usage  
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more
First Contentful Paint (3G) 2865 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.4 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
First CPU Idle 1.4 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. . Learn more
First Contentful Paint 1.4 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
Performance budget  
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more

Does fxurl.date 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 fxurl.date are reduced by 65%.
fxurl.date use br compression.
Original size: 2.18 KB
Compressed size: 775 B
File reduced by: 1.42 KB (65%)

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

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. fxurl.date supports HTTPS.
 fxurl.date supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: fxurl.date
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 15 14:00:33 2019 GMT
Valid until: Feb 13 14:00:33 2020 GMT
Authority:
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.
 fxurl.date 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.
Connection: Keep-Alive
X-Powered-By: PHP/5.5.38
Expires: Thu, 23 Mar 1972 07:00:00 GMT
Last-Modified: Sun, 29 Dec 2019 16:09:03 GMT
Cache-Control: no-cache, must-revalidate, max-age=0
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Content-Length: 775
Content-Encoding: br
Vary: Accept-Encoding
Date: Sun, 29 Dec 2019 16:09:03 GMT
Server: LiteSpeed

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
TXT v=spf1 ip4:138.128.174.10 +a +mx +ip4:5.101.174.57 include:thewebhostserver.com ~all 3600
MX fxurl.date 3600
SOA 3600
Mname dns1.peekhosting.com
Rname sajith.gsm.gmail.com
Serial Number 2019121400
Refresh 3600
Retry 1800
Expire 1209600
Minimum TTL 86400
A 138.128.174.10 3583
NS dns2.peekhosting.com 3582
NS dns1.peekhosting.com 3582

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. Domain registration for this website began on June 2, 2018 and will expire on March 28, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on March 28, 2024.
Domain Created:
2018-06-02
Domain Age:
5 years 9 months 26 days
WhoIs:
 

whois lookup at whois.nic.date...Domain Name: fxurl.date
Registry Domain ID: DEF8F7F57751B4EEC8FDCCCB5C5E391F1-NSR
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2019-08-31T13:57:43Z
Creation Date: 2018-06-02T03:42:13Z
Registry Expiry Date: 2020-06-02T03:42:13Z
Registrar: NameCheap, Inc.
Registrar IANA ID: 1068
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.6613102107
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID:
Registrant Name:
Registrant Organization: WhoisGuard, Inc.
Registrant Street:
Registrant Street:
Registrant Street:
Registrant City:
Registrant State/Province: Panama
Registrant Postal Code:
Registrant Country: PA
Registrant Phone:
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID:
Admin Name:
Admin Organization:
Admin Street:
Admin Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID:
Tech Name:
Tech Organization:
Tech Street:
Tech Street:
Tech Street:
Tech City:
Tech State/Province:
Tech Postal Code:
Tech Country:
Tech Phone:
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: ns4.peekhosting.com
Name Server: ns2.peekhosting.com
Name Server: ns1.peekhosting.com
Name Server: ns3.peekhosting.com
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2019-12-29T16:09:21Z <<<
The above WHOIS results have been redacted to remove potential personal data. The full WHOIS output may be available to individuals and organisations with a legitimate interest in accessing this data not outweighed by the fundamental privacy rights of the data subject. To find out more, or to make a request for access, please visit: RDDSrequest.nic.date.
For more information on Whois status codes, please visit https://icann.org/epp

The WHOIS service offered by the Registry Operator, and the access to the records in the Registry Operator WHOIS database, are provided for information purposes only and is designed (i) to assist persons in determining whether a specific domain name registration record is available or not in the Registry Operator database and (ii) to obtain information related to the registration records of existing domain names.  The Registry Operator cannot, under any circumstances, be held liable in such instances where the stored information would prove to be wrong, incomplete, or not accurate in any sense. 
By submitting a WHOIS query, you, the user, agree that you will not use this data: 
(i)	to allow, enable or otherwise support in any way the transmission of unsolicited, commercial advertising or other solicitations whether via direct mail, email, telephone or otherwise; 
(ii)	to enable high volume, automated, electronic processes that apply to the registry (or its systems); 
(iii)	for target advertising in any possible way; 
(iv)	to cause nuisance in any possible way to the registrants by sending (whether by automated, electronic processes capable of enabling high volumes or other possible means) messages to them; 
(v)	to violate any law, rule, regulation or statute; and/or 
(vi)	in contravention of any applicable data and privacy protection acts. 

Without prejudice to the above, it is explicitly forbidden to extract, copy and/or use or re-utilize in any form and by any means (electronically or not) the whole or a quantitatively or qualitatively substantial part of the contents of the WHOIS database without prior and explicit permission by Registry Operator, nor in any attempt hereof, or to apply automated, electronic processes to Registry Operator (or its systems or their designated third party Registry Service Provider's systems). 

You agree that any reproduction and/or transmission of data for commercial purposes will always be considered as the extraction of a substantial part of the content of the WHOIS database. By utilizing this website and/or submitting a query you agree to abide by this policy and accept that Registry Operator can take measures to limit the use of its WHOIS services in order to protect the privacy of its registrants or the integrity of the database. 

We reserve the right to make changes to these Terms and Conditions at any time without prior notice to you. It is your responsibility to review these Terms and Conditions each time you access or use the WHOIS service and to familiarise yourself with any changes. If you do not agree to the changes implemented by Registry Operator, your sole and exclusive remedy is to terminate your use of the WHOIS service. 

By executing a query, in any manner whatsoever, you agree to abide by these Terms and Conditions. 
NOTE: FAILURE TO LOCATE A RECORD IN THE WHOIS DATABASE IS NOT INDICATIVE OF THE AVAILABILITY OF A DOMAIN NAME.