GMX.COM Free Email Accounts @GMX.com: Secure & easy to use


gmx.com website information.

gmx.com domain name is registered by .COM top-level domain registry. See the other sites registred in .COM domain zone.

Following name servers are specified for gmx.com domain:

  • ns-gmx.ui-dns.org
  • ns-gmx.ui-dns.biz
  • ns-gmx.ui-dns.de
  • ns-gmx.ui-dns.com

and probably website gmx.com is hosted by TFN-TW Taiwan Fixed Network, Telco and Network Service Provider., TW web hosting company. Check the complete list of other most popular websites hosted by TFN-TW Taiwan Fixed Network, Telco and Network Service Provider., TW hosting company.

According to Alexa traffic rank the highest website gmx.com position was 15239 (in the world). The lowest Alexa rank position was 18438. Now website gmx.com ranked in Alexa database as number 17708 (in the world).

Website gmx.com Desktop speed measurement score (76/100) is better than the results of 61.81% of other sites shows that the page desktop performance can be improved.

gmx.com Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of gmx.com (51/100) is better than the results of 35.73% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Mar-29-2024 17,708106
Mar-28-2024 17,814-39
Mar-27-2024 17,775-134
Mar-26-2024 17,64182
Mar-25-2024 17,72345
Mar-24-2024 17,76810
Mar-23-2024 17,778-43

Advertisement

gmx.com 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.



gmx.com 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.


Domain Name: GMX.COM
Registry Domain ID: 3407380_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.psi-usa.info
Registrar URL: http://www.psi-usa.info
Updated Date: 2021-05-09T07:01:39Z
Creation Date: 1994-05-07T04:00:00Z
Registry Expiry Date: 2022-05-08T04:00:00Z
Registrar: PSI-USA, Inc. dba Domain Robot
Registrar IANA ID: 151
Registrar Abuse Contact Email: domain-abuse@psi-usa.info
Registrar Abuse Contact Phone: +49.94159559482
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: NS-GMX.UI-DNS.BIZ
Name Server: NS-GMX.UI-DNS.COM
Name Server: NS-GMX.UI-DNS.DE
Name Server: NS-GMX.UI-DNS.ORG
DNSSEC: signedDelegation
DNSSEC DS Data: 32227 8 2 DF6BC2D9BF3AF1913BA2DB52C9B40BA03935521C017176DE213CBA4CF8EC7F3D
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2021-12-30T07:30:33Z

gmx.com server information

Servers Location

IP Address
82.165.229.87
Country
Germany
Region
Baden-Wurttemberg
City
Karlsruhe

gmx.com desktop page speed rank

Last tested: 2019-08-16


Desktop Speed Medium
76/100

gmx.com Desktop Speed Test Quick Summary


priority - 9 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://gmx.com/
https://gmx.com/
https://www.gmx.com/

priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 5 blocking script resources and 2 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:

https://dl.gmx.com/uim/bidding/consent.js
https://s.uicdn.com/mailint/8.1251.0/assets/head.min.js
https://s.uicdn.com/mailint/8.1251.0/assets/adservice.js
https://static.criteo.net/js/px.js?ch=1
https://static.criteo.net/js/px.js?ch=2

Optimize CSS Delivery of the following:

https://s.uicdn.com/mailint/8.1251.0/assets/styles.gmxcom.min.css
https://fonts.googleapis.com/css?family=Droid+Sans…atin,latin,latin,latin

priority - 5 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:

https://www.googletagmanager.com/gtm.js?id=GTM-58QWRT (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://js-sec.indexww.com/ht/p/183560-142256617093748.js (17.2 minutes)
https://www.googletagservices.com/activeview/js/cu…osd.js?cb=%2Fr20100101 (50 minutes)
https://www.googletagservices.com/activeview/js/cu…ner.js?cache=r20110914 (50 minutes)
https://one-and-one-d.openx.net/w/1.0/jstag?nc=6840-gmx.com (60 minutes)
https://tags.expo9.exponential.com/tags/gmxfr/ROS/tags.js (60 minutes)
https://www.googleadservices.com/pagead/conversion_async.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://dl.gmx.com/uim/bidding/consent.js (5 hours)

priority - 4 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 43.3KiB (78% reduction).

Compressing https://api.taboola.com/1.2/json/1and1internet-gmx…t2.thumbnail.width=620 could save 20.7KiB (83% reduction).
Compressing https://15.cbarsrv.com/BidRHanSer?oid=15&width=4,7…Fwww.gmx.com%2F&cisrf= could save 20.4KiB (81% reduction).
Compressing https://us-u.openx.net/w/1.0/pd?plm=10&ph=2ab75175…4c37-abc5-657feae9086c could save 543B (48% reduction).
Compressing https://us-u.openx.net/w/1.0/pd?plm=10&ph=2ab75175…4c37-abc5-657feae9086c could save 364B (42% reduction).
Compressing https://one-and-one-d.openx.net/w/1.0/acj?ai=25978…86c&ba=1565935467&sd=1 could save 224B (42% reduction).
Compressing https://one-and-one-d.openx.net/w/1.0/acj?ai=25978…86c&ba=1565935467&sd=1 could save 224B (42% reduction).
Compressing https://one-and-one-d.openx.net/w/1.0/acj?ai=25978…86c&ba=1565935467&sd=1 could save 224B (42% reduction).
Compressing https://one-and-one-d.openx.net/w/1.0/acj?cc=1&ai=…86c&ba=1565935467&sd=1 could save 224B (42% reduction).
Compressing https://one-and-one-d.openx.net/w/1.0/acj?cc=1&ai=…86c&ba=1565935467&sd=1 could save 223B (41% reduction).
Compressing https://static.criteo.net/js/px.js?ch=1 could save 110B (32% reduction).
Compressing https://static.criteo.net/js/px.js?ch=2 could save 110B (32% reduction).

priority - 2 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 43% of the final above-the-fold content could be rendered with the full HTML response.
Click to see the screenshot with only the HTML response:

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 11.1KiB (13% reduction).

Compressing https://images.taboola.com/taboola/image/fetch/f_j…a65733864b78a31053.png could save 8KiB (13% reduction).
Compressing https://images.taboola.com/taboola/image/fetch/f_j…4ab8193eb4b8046118.jpg could save 2.8KiB (13% reduction).
Compressing https://s.uicdn.com/mailint/8.1251.0/assets/navigation/icon_signup.png could save 303B (28% reduction).

priority - 0 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.7KiB (26% reduction).

Minifying https://tags.expo9.exponential.com/tags/gmxfr/ROS/tags.js could save 3.9KiB (29% reduction) after compression.
Minifying https://live.sekindo.com/live/liveView.php?s=10008…&subId=[SUBID_ENCODED] could save 844B (17% reduction) after compression.

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 271B (12% reduction).

Minifying https://vidstat.taboola.com/vpaid/vPlayer/player/v….110/assets/player.css could save 271B (12% reduction) after compression.

gmx.com Desktop Resources

Total Resources239
Number of Hosts82
Static Resources78
JavaScript Resources52
CSS Resources4

gmx.com Desktop Resource Breakdown

gmx.com mobile page speed rank

Last tested: 2017-11-29


Mobile Speed Bad
51/100

gmx.com Mobile Speed Test Quick Summary


priority - 64 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 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:

https://s.uicdn.com/mailint/8.887.0/assets/head.min.js
https://s.uicdn.com/mailint/8.887.0/assets/adservice.js

Optimize CSS Delivery of the following:

https://s.uicdn.com/mailint/8.887.0/assets/styles.gmxcom.min.css
https://fonts.googleapis.com/css?family=Droid+Sans…atin,latin,latin,latin

priority - 34 Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://gmx.com/
https://gmx.com/
https://www.gmx.com/

priority - 4 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:

https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
https://js-sec.indexww.com/ht/maildotcom.js (29.5 minutes)
https://one-and-one-d.openx.net/w/1.0/jstag?nc=6840-gmx.com (60 minutes)
https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)

priority - 2 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 19.8KiB (16% reduction).

Compressing https://i0.gmx.com/gcom/838/4685838%2Cpd=2%2Cf=teaser-list-l/.jpg could save 6.6KiB (20% reduction).
Compressing https://i1.gmx.com/gcom/836/4685836%2Cpd=2%2Cf=teaser-list-l/.jpg could save 5.5KiB (17% reduction).
Compressing https://i1.gmx.com/gcom/438/3733438,pd=2/.jpg could save 5KiB (14% reduction).
Compressing https://i0.gmx.com/gcom/796/4775796,pd=1/.jpg could save 2.7KiB (14% reduction).

gmx.com Mobile Resources

Total Resources127
Number of Hosts33
Static Resources59
JavaScript Resources33
CSS Resources5

gmx.com Mobile Resource Breakdown

gmx.com mobile page usability

Last tested: 2017-11-29


Mobile Usability Good
99/100

gmx.com Mobile Usability Test Quick Summary


priority - 0 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.

The tap target <a href="https://www.facebook.com/GMX" class="fb">facebook</a> and 2 others are close to other tap targets.

gmx.com similar domains

Similar domains:
www.gmx.com
www.gmx.net
www.gmx.org
www.gmx.info
www.gmx.biz
www.gmx.us
www.gmx.mobi
www.mx.com
www.gmx.com
www.fmx.com
www.gfmx.com
www.fgmx.com
www.vmx.com
www.gvmx.com
www.vgmx.com
www.tmx.com
www.gtmx.com
www.tgmx.com
www.bmx.com
www.gbmx.com
www.bgmx.com
www.ymx.com
www.gymx.com
www.ygmx.com
www.hmx.com
www.ghmx.com
www.hgmx.com
www.gx.com
www.gnx.com
www.gmnx.com
www.gnmx.com
www.gjx.com
www.gmjx.com
www.gjmx.com
www.gkx.com
www.gmkx.com
www.gkmx.com
www.gm.com
www.gmz.com
www.gmxz.com
www.gmzx.com
www.gms.com
www.gmxs.com
www.gmsx.com
www.gmd.com
www.gmxd.com
www.gmdx.com
www.gmc.com
www.gmxc.com
www.gmcx.com
www.gmx.con

gmx.com 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.


gmx.com 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.