42.fr website information.
42.fr domain name is registered by .FR top-level domain registry. See the other sites registred in .FR domain zone.
Following name servers are specified for 42.fr domain:
- ns1.42.fr
- ns2.42.fr
and probably website 42.fr is hosted by AMAZON-02 - Amazon.com, Inc., US web hosting company. Check the complete list of other most popular websites hosted by AMAZON-02 - Amazon.com, Inc., US hosting company.
According to Alexa traffic rank the highest website 42.fr position was 96934 (in the world). The lowest Alexa rank position was 193025. Now website 42.fr ranked in Alexa database as number 100154 (in the world).
Website 42.fr Desktop speed measurement score (86/100) is better than the results of 82.23% of other sites and shows that the page is performing great on desktop computers.
42.fr Mobile usability score (88/100) is better than the results of 28.85% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of 42.fr (75/100) is better than the results of 84.42% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Sep-22-2024 | 100,154 | 2,133 |
| Sep-21-2024 | 102,287 | -2,286 |
| Sep-20-2024 | 100,001 | -421 |
| Sep-19-2024 | 99,580 | 1,182 |
| Sep-18-2024 | 100,762 | 1,288 |
| Sep-17-2024 | 102,050 | -652 |
| Sep-16-2024 | 101,398 | -4,464 |
Advertisement
42.fr Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
42.fr whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
%%
%% This is the AFNIC Whois server.
%%
%% complete date format : YYYY-MM-DDThh:mm:ssZ
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See https://www.afnic.fr/en/products-and-services/services/whois/whois-special-notice/
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [167.99.102.248 REQUEST] >> 42.fr
%%
%% RL Net [##########] - RL IP [#########.]
%%
domain: 42.fr
status: ACTIVE
hold: NO
holder-c: AQ2123-FRNIC
admin-c: ANO00-FRNIC
tech-c: GR283-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL488654-FRNIC
registrar: GANDI
Expiry Date: 2026-05-31T22:07:29Z
created: 2004-05-26T17:32:49Z
last-update: 2020-11-06T16:12:02Z
source: FRNIC
ns-list: NSL488654-FRNIC
nserver: ns-64-a.gandi.net
nserver: ns-224-c.gandi.net
nserver: ns-26-b.gandi.net
source: FRNIC
registrar: GANDI
type: Isp Option 1
address: 63-65 boulevard Massena
address: 75013 PARIS
country: FR
phone: +33 1 70 37 76 61
fax-no: +33 1 43 73 18 51
e-mail: support@support.gandi.net
website: https://www.gandi.net/fr/tlds/fr/
anonymous: NO
registered: 2004-03-09T12:00:00Z
source: FRNIC
nic-hdl: AQ2123-FRNIC
type: ORGANIZATION
contact: ASSOCIATION 42
address: ASSOCIATION 42
address: 96 BD BESSIERES
address: 75017 PARIS
address: 11
country: FR
phone: +33.142281284
e-mail: 6f68aaa0fe977c053ed8f1e926f1abca-15543727@contact.gandi.net
registrar: GANDI
changed: 2019-10-10T11:52:37Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC
nic-hdl: ANO00-FRNIC
type: PERSON
contact: Ano Nymous
remarks: -------------- WARNING --------------
remarks: While the registrar knows him/her,
remarks: this person chose to restrict access
remarks: to his/her personal data. So PLEASE,
remarks: don't send emails to Ano Nymous. This
remarks: address is bogus and there is no hope
remarks: of a reply.
remarks: -------------- WARNING --------------
registrar: GANDI
changed: 2019-05-31T22:13:14Z anonymous@anonymous
anonymous: YES
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC
nic-hdl: GR283-FRNIC
type: ROLE
contact: GANDI ROLE
address: Gandi
address: 15, place de la Nation
address: 75011 Paris
country: FR
e-mail: noc@gandi.net
trouble: -------------------------------------------------
trouble: GANDI is an ICANN accredited registrar
trouble: for more information:
trouble: Web: http://www.gandi.net
trouble: -------------------------------------------------
trouble: - network troubles: noc@gandi.net
trouble: - SPAM: abuse@support.gandi.net
trouble: -------------------------------------------------
admin-c: NL346-FRNIC
tech-c: NL346-FRNIC
tech-c: TUF1-FRNIC
notify: noc@gandi.net
registrar: GANDI
changed: 2006-03-03T14:39:12Z noc@gandi.net
anonymous: NO
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC
42.fr server information
42.fr desktop page speed rank
Last tested: 2018-12-08
42.fr Desktop Speed Test Quick Summary
priority - 7 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://www.42.fr/wp-content/themes/42/fonts/Quicksand_Bold.woff (expiration not specified)
http://www.42.fr/wp-content/themes/42/fonts/Quicksand_Book.woff (expiration not specified)
http://www.42.fr/wp-content/themes/42/fonts/ic42.woff (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/42-polymorph2.png (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/42-polymorph3.png (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/logo42-site.gif (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/site42-bg.gif (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/site42-bghome.png (expiration not specified)
http://www.42.fr/wp-content/themes/42/js/main.js (expiration not specified)
http://www.42.fr/wp-content/themes/42/js/plugins-min.js (expiration not specified)
http://www.42.fr/wp-content/themes/42/js/vendor/modernizr-2.6.2.min.js (expiration not specified)
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js (50 minutes)
http://js-agent.newrelic.com/nr-100.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
priority - 4 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
priority - 2 Reduce server response time
In our test, your server responded in 0.42 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 0 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 2.7KiB (12% reduction).
Losslessly compressing http://www.42.fr/wp-content/themes/42/img/42-polymorph3.png could save 707B (22% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 748B (17% reduction).
42.fr Desktop Resources
| Total Resources | 29 |
| Number of Hosts | 7 |
| Static Resources | 22 |
| JavaScript Resources | 11 |
| CSS Resources | 1 |
42.fr Desktop Resource Breakdown
42.fr mobile page speed rank
Last tested: 2018-12-08
42.fr Mobile Speed Test Quick Summary
priority - 16 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
priority - 10 Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://www.42.fr/wp-content/themes/42/fonts/Quicksand_Bold.woff (expiration not specified)
http://www.42.fr/wp-content/themes/42/fonts/Quicksand_Book.woff (expiration not specified)
http://www.42.fr/wp-content/themes/42/fonts/ic42.woff (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/42-polymorph2.png (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/42-polymorph3.png (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/logo42-site.gif (expiration not specified)
http://www.42.fr/wp-content/themes/42/img/site42-bg.gif (expiration not specified)
http://www.42.fr/wp-content/themes/42/js/main.js (expiration not specified)
http://www.42.fr/wp-content/themes/42/js/plugins-min.js (expiration not specified)
http://www.42.fr/wp-content/themes/42/js/vendor/modernizr-2.6.2.min.js (expiration not specified)
http://www.google.com/recaptcha/api/js/recaptcha_ajax.js (50 minutes)
http://js-agent.newrelic.com/nr-100.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)
priority - 6 Reduce server response time
In our test, your server responded in 0.58 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 0 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 707B (22% reduction).
priority - 0 Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 745B (17% reduction).
42.fr Mobile Resources
| Total Resources | 28 |
| Number of Hosts | 7 |
| Static Resources | 21 |
| JavaScript Resources | 11 |
| CSS Resources | 1 |
42.fr Mobile Resource Breakdown
42.fr mobile page usability
Last tested: 2018-12-08
42.fr Mobile Usability Test Quick Summary
priority - 11 Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="http://www.42.…our-la-france/">Pour la France</a> and 15 others are close to other tap targets.<a href="https://twitte…om/42born2code">t</a> and 2 others are close to other tap targets.42.fr similar domains
www.42.net
www.42.org
www.42.info
www.42.biz
www.42.us
www.42.mobi
www.2.fr
www.42.fr
www.4.fr
42.fr Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
42.fr TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.