INFOMED39.RU Главная | Министерство здравоохранения Калининградской области


infomed39.ru website information.

infomed39.ru domain name is registered by .RU top-level domain registry. See the other sites registred in .RU domain zone.

Following name servers are specified for infomed39.ru domain:

  • ns8-l2.nic.ru
  • ns8-cloud.nic.ru
  • ns4-cloud.nic.ru
  • ns3-l2.nic.ru
  • ns4-l2.nic.ru

and probably website infomed39.ru is hosted by UNICOM-GUANGZHOU-IDC China Unicom Guangdong IP network, CN web hosting company. Check the complete list of other most popular websites hosted by UNICOM-GUANGZHOU-IDC China Unicom Guangdong IP network, CN hosting company.

According to Alexa traffic rank the highest website infomed39.ru position was 20959 (in the world). The lowest Alexa rank position was 998929. Now website infomed39.ru ranked in Alexa database as number 738398 (in the world).

Website infomed39.ru Desktop speed measurement score (74/100) is better than the results of 57.94% of other sites shows that the page desktop performance can be improved.

infomed39.ru Mobile usability score (96/100) is better than the results of 46.59% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of infomed39.ru (52/100) is better than the results of 37.6% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Nov-19-2024 738,39819,589
Nov-18-2024 757,987-9,092
Nov-17-2024 748,895-738
Nov-16-2024 748,157-11,766
Nov-15-2024 736,391-755
Nov-14-2024 735,636-2,845
Nov-13-2024 732,7910

Advertisement

infomed39.ru 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.



infomed39.ru 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.


% By submitting a query to RIPN's Whois Service
% you agree to abide by the following terms of use:
% http://www.ripn.net/about/servpol.html#3.2 (in Russian)
% http://www.ripn.net/about/en/servpol.html#3.2 (in English).

domain: INFOMED39.RU
nserver: ns3-l2.nic.ru.
nserver: ns4-l2.nic.ru.
nserver: ns8-l2.nic.ru.
state: REGISTERED, DELEGATED, VERIFIED
org: GKUZ MIAC
registrar: RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created: 2007-09-19T20:00:00Z
paid-till: 2022-09-19T21:00:00Z
free-date: 2022-10-21
source: TCI

Last updated on 2022-01-03T14:11:30Z

infomed39.ru server information

Servers Location

IP Address
2.63.255.202
83.219.143.95
Region
Novosibirskaya oblast'
Kaliningradskaya oblast'
City
Novosibirsk
Chernyakhovsk

infomed39.ru desktop page speed rank

Last tested: 2019-09-06


Desktop Speed Medium
74/100

infomed39.ru Desktop Speed Test Quick Summary


priority - 14 Avoid landing page redirects

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

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

http://infomed39.ru/
https://infomed39.ru/
http://www.infomed39.ru/
https://www.infomed39.ru/

priority - 9 Optimize images

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

Optimize the following images to reduce their size by 83.6KiB (51% reduction).

Compressing https://www.infomed39.ru/local/templates/.default/img/logo-big.jpg could save 48.3KiB (73% reduction).
Compressing https://www.infomed39.ru/local/templates/.default/img/main-logo-mobile.jpg could save 14.8KiB (69% reduction).
Compressing https://www.infomed39.ru/local/templates/.default/img/logo-footer.jpg could save 11.5KiB (69% reduction).
Compressing https://www.infomed39.ru/upload/iblock/359/3598fb6…715eb6b5422bfe81f8.jpg could save 2.7KiB (15% reduction).
Compressing https://www.infomed39.ru/upload/iblock/77b/77b5d00…129c7a1888d79a1cd5.jpg could save 2.6KiB (17% reduction).
Compressing https://www.infomed39.ru/upload/iblock/cdc/cdc767c…d23fdcf520a1485dcc.jpg could save 2.2KiB (16% reduction).
Compressing https://www.infomed39.ru/upload/iblock/dc9/dc9b0e9…0779ef9f2c48fbb270.jpg could save 1KiB (13% reduction).
Compressing https://www.infomed39.ru/local/templates/.default/img/icon-apple-store.png could save 427B (44% reduction).

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://api-maps.yandex.ru/2.0/images/2c3d90d4e522c1f62b6cf3e59f7a877d.png (expiration not specified)
https://api-maps.yandex.ru/2.0/images/3ce22e999d54bb9ca8150a59207f9d3e.cur (expiration not specified)
https://api-maps.yandex.ru/2.0/images/4965b66fe115b2f2ed500ece66514d86.cur (expiration not specified)
https://api-maps.yandex.ru/2.0/images/77492cf358d8b12629399322926c93f2.cur (expiration not specified)
https://api-maps.yandex.ru/2.0/images/ef50ac9e93aaebe3299791c79f277f8e.cur (expiration not specified)
https://api-maps.yandex.ru/services/inception/inception.js (expiration not specified)
https://bitrix.info/bx_stat (expiration not specified)
https://api-maps.yandex.ru/2.0/?load=package.full&…ng=ru-RU&wizard=bitrix (5 minutes)
https://mc.yandex.ru/metrika/advert.gif (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://stat.sputnik.ru/cnt.js (60 minutes)

priority - 4 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 35KiB (26% reduction).

Minifying https://www.infomed39.ru/bitrix/js/main/core/core.js?1566973497497598 could save 29.2KiB (26% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_fx.js?153234784116888 could save 1.1KiB (27% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_db.js?153234784120929 could save 1.1KiB (29% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…table.js/stacktable.js could save 890B (44% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_…che.js?153562875217797 could save 815B (17% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/js/main.js could save 762B (54% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/js/override.js could save 549B (27% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_ls.js?153234784110430 could save 503B (20% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…/i18n/datepicker-ru.js could save 176B (23% reduction) after compression.

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

Your page has 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.

Optimize CSS Delivery of the following:

https://www.infomed39.ru/bitrix/js/main/core/css/core.css?15323478413963

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 3.9KiB (20% reduction).

Minifying https://www.infomed39.ru/local/templates/.default/…ui.css?153234782037284 could save 1.4KiB (17% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…in.css?156171163968360 could save 1.4KiB (18% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/css/core.css?15323478413963 could save 547B (40% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…ide.css?15323478206542 could save 318B (17% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…eme.css?15323478201743 could save 199B (33% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…sel.css?15323478201547 could save 122B (23% reduction) after compression.

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 1.5KiB (12% reduction).

Minifying https://www.infomed39.ru/ could save 1.5KiB (12% reduction) after compression.

priority - 0 Reduce server response time

In our test, your server responded in 0.21 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.

infomed39.ru Desktop Resources

Total Resources95
Number of Hosts10
Static Resources83
JavaScript Resources27
CSS Resources14

infomed39.ru Desktop Resource Breakdown

infomed39.ru mobile page speed rank

Last tested: 2019-08-25


Mobile Speed Bad
52/100

infomed39.ru Mobile Speed Test Quick Summary


priority - 51 Avoid landing page redirects

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

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

http://infomed39.ru/
https://infomed39.ru/
http://www.infomed39.ru/
https://www.infomed39.ru/

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

Your page has 14 blocking script resources and 15 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://www.infomed39.ru/bitrix/js/main/core/core.js?1555667673123541
https://www.infomed39.ru/bitrix/js/main/core/core_promise.js?15556676935220
https://www.infomed39.ru/bitrix/js/main/polyfill/p…mise.js?15373420188241
https://www.infomed39.ru/bitrix/js/main/core/core_ajax.js?155566769341997
https://www.infomed39.ru/bitrix/js/main/loadext/loadext.js?15409884322917
https://www.infomed39.ru/bitrix/js/main/loadext/extension.js?15409884322895
https://www.infomed39.ru/bitrix/js/main/core/core_db.js?153234784120929
https://www.infomed39.ru/bitrix/js/main/json/json2.min.js?15323478403467
https://www.infomed39.ru/bitrix/js/main/core/core_ls.js?153234784110430
https://www.infomed39.ru/bitrix/js/main/core/core_fx.js?153234784116888
https://www.infomed39.ru/bitrix/js/main/core/core_…che.js?153562875217797
https://www.infomed39.ru/bitrix/js/main/core/core_window.js?154098843297989
https://www.infomed39.ru/local/templates/.default/…min.js?153234782086663
https://www.infomed39.ru/bitrix/components/bitrix/…ript.js?15323478211540

Optimize CSS Delivery of the following:

https://www.infomed39.ru/bitrix/css/intervolga.pri…les.css?15451415522310
https://www.infomed39.ru/bitrix/js/main/core/css/core.css?15323478413963
https://www.infomed39.ru/local/templates/.default/…in.css?153234782031004
https://www.infomed39.ru/local/templates/.default/…ui.css?153234782037284
https://www.infomed39.ru/local/templates/.default/…sel.css?15323478201547
https://www.infomed39.ru/local/templates/.default/…eme.css?15323478201743
https://www.infomed39.ru/local/templates/.default/…able.css?1532347820485
https://www.infomed39.ru/local/templates/.default/…in.css?153234782013706
https://www.infomed39.ru/local/templates/master/pa…tabs.css?1532347819573
https://www.infomed39.ru/local/templates/.default/…in.css?156171163968360
https://www.infomed39.ru/local/templates/.default/…ide.css?15323478206542
https://www.infomed39.ru/bitrix/components/bitrix/…tyle.css?1532347823745
https://www.infomed39.ru/bitrix/panel/main/popup.css?153234782623084
https://www.infomed39.ru/local/templates/.default/…tyle.css?1532347820112
https://www.infomed39.ru/local/components/bitrix/m…tyle.css?1532347819666

priority - 8 Optimize images

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

Optimize the following images to reduce their size by 80.9KiB (55% reduction).

Compressing https://www.infomed39.ru/local/templates/.default/img/logo-big.jpg could save 48.3KiB (73% reduction).
Compressing https://www.infomed39.ru/local/templates/.default/img/main-logo-mobile.jpg could save 14.8KiB (69% reduction).
Compressing https://www.infomed39.ru/local/templates/.default/img/logo-footer.jpg could save 11.5KiB (69% reduction).
Compressing https://www.infomed39.ru/upload/iblock/359/3598fb6…715eb6b5422bfe81f8.jpg could save 2.7KiB (15% reduction).
Compressing https://www.infomed39.ru/upload/iblock/cdc/cdc767c…d23fdcf520a1485dcc.jpg could save 2.2KiB (16% reduction).
Compressing https://www.infomed39.ru/upload/iblock/dc9/dc9b0e9…0779ef9f2c48fbb270.jpg could save 1KiB (13% reduction).
Compressing https://www.infomed39.ru/local/templates/.default/img/icon-apple-store.png could save 427B (44% reduction).

priority - 8 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://api-maps.yandex.ru/2.0/images/2c3d90d4e522c1f62b6cf3e59f7a877d.png (expiration not specified)
https://api-maps.yandex.ru/2.0/images/3ce22e999d54bb9ca8150a59207f9d3e.cur (expiration not specified)
https://api-maps.yandex.ru/2.0/images/4965b66fe115b2f2ed500ece66514d86.cur (expiration not specified)
https://api-maps.yandex.ru/2.0/images/77492cf358d8b12629399322926c93f2.cur (expiration not specified)
https://api-maps.yandex.ru/2.0/images/ef50ac9e93aaebe3299791c79f277f8e.cur (expiration not specified)
https://api-maps.yandex.ru/services/inception/inception.js (expiration not specified)
https://bitrix.info/bx_stat (expiration not specified)
https://api-maps.yandex.ru/2.0/?load=package.full&…ng=ru-RU&wizard=bitrix (5 minutes)
https://mc.yandex.ru/metrika/advert.gif (60 minutes)
https://mc.yandex.ru/metrika/watch.js (60 minutes)
https://stat.sputnik.ru/cnt.js (60 minutes)

priority - 2 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 20.2KiB (23% reduction).

Minifying https://www.infomed39.ru/bitrix/js/main/core/core.js?1555667673123541 could save 5.8KiB (20% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_window.js?154098843297989 could save 3.5KiB (18% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_ajax.js?155566769341997 could save 2.6KiB (24% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_fx.js?153234784116888 could save 1.1KiB (27% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_db.js?153234784120929 could save 1.1KiB (29% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/polyfill/p…mise.js?15373420188241 could save 1KiB (48% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…table.js/stacktable.js could save 890B (44% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_…che.js?153562875217797 could save 815B (17% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/js/main.js could save 762B (54% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_promise.js?15556676935220 could save 686B (46% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/js/override.js could save 549B (27% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/core_ls.js?153234784110430 could save 503B (20% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/loadext/loadext.js?15409884322917 could save 416B (43% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/loadext/extension.js?15409884322895 could save 305B (31% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…/i18n/datepicker-ru.js could save 176B (23% 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 4.4KiB (18% reduction).

Minifying https://www.infomed39.ru/local/templates/.default/…ui.css?153234782037284 could save 1.4KiB (17% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…in.css?156171163968360 could save 1.4KiB (18% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/js/main/core/css/core.css?15323478413963 could save 547B (40% reduction) after compression.
Minifying https://www.infomed39.ru/bitrix/panel/main/popup.css?153234782623084 could save 477B (12% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…ide.css?15323478206542 could save 318B (17% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…eme.css?15323478201743 could save 199B (33% reduction) after compression.
Minifying https://www.infomed39.ru/local/templates/.default/…sel.css?15323478201547 could save 122B (23% reduction) after compression.

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 1.5KiB (12% reduction).

Minifying https://www.infomed39.ru/ could save 1.5KiB (12% reduction) after compression.

infomed39.ru Mobile Resources

Total Resources94
Number of Hosts10
Static Resources82
JavaScript Resources34
CSS Resources15

infomed39.ru Mobile Resource Breakdown

infomed39.ru mobile page usability

Last tested: 2019-08-25


Mobile Usability Good
96/100

infomed39.ru Mobile Usability Test Quick Summary


priority - 3 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="#shop-product-tab-2" class="shop-product-t…r-tabs-anchor">Публикации</a> is close to 1 other tap targets.

The tap target <a href="/press-center/…nior-citizens/">С начала года…илого возраста</a> and 5 others are close to other tap targets.
The tap target <a href="/press-center/" class="btn btn-white-outline">Все публикации</a> and 1 others are close to other tap targets.

The tap target <a href="mailto:site@infomed39.ru">site@infomed39.ru</a> and 2 others are close to other tap targets.
The tap target <a href="#hidden-content-d">Авторизация</a> is close to 2 other tap targets.
The tap target <a href="http://miac39.ru/">МИАЦ</a> is close to 1 other tap targets.
The tap target <ymaps class="ymaps-copyrights-pane">© ЯндексУсловия использования</ymaps> is close to 3 other tap targets.
The tap target <a href="https://yandex…715082&amp;z=14&amp;l=" class="ymaps-logo-lin…s-logo-link-ru"></a> is close to 4 other tap targets.
The tap target <a href="https://yandex…ofuse/?lang=ru">Условия использования</a> is close to 2 other tap targets.
The tap target <ymaps class="ymaps-b-zoom_hints-pos_right">мирстранагородулицадом</ymaps> and 1 others are close to other tap targets.
The tap target <ymaps class="ymaps-b-zoom__…ton_type_minus"></ymaps> and 1 others are close to other tap targets.
The tap target <ymaps class="ymaps-b-zoom__scale-bg"> is close to 1 other tap targets.
The tap target <ymaps class="ymaps-b-zoom__mark"></ymaps> is close to 1 other tap targets.
The tap target <ymaps class="ymaps-b-zoom__…tton_type_plus"></ymaps> and 1 others are close to other tap targets.
The tap target <ymaps>400 м</ymaps> and 1 others are close to other tap targets.
The tap target <ymaps>400 м</ymaps> and 1 others are close to other tap targets.
The tap target <ymaps class="ymaps-point-overlay"></ymaps> and 1 others are close to other tap targets.

infomed39.ru similar domains

Similar domains:
www.infomed39.com
www.infomed39.net
www.infomed39.org
www.infomed39.info
www.infomed39.biz
www.infomed39.us
www.infomed39.mobi
www.nfomed39.ru
www.infomed39.ru
www.unfomed39.ru
www.iunfomed39.ru
www.uinfomed39.ru
www.jnfomed39.ru
www.ijnfomed39.ru
www.jinfomed39.ru
www.knfomed39.ru
www.iknfomed39.ru
www.kinfomed39.ru
www.onfomed39.ru
www.ionfomed39.ru
www.oinfomed39.ru
www.ifomed39.ru
www.ibfomed39.ru
www.inbfomed39.ru
www.ibnfomed39.ru
www.ihfomed39.ru
www.inhfomed39.ru
www.ihnfomed39.ru
www.ijfomed39.ru
www.injfomed39.ru
www.imfomed39.ru
www.inmfomed39.ru
www.imnfomed39.ru
www.inomed39.ru
www.incomed39.ru
www.infcomed39.ru
www.incfomed39.ru
www.indomed39.ru
www.infdomed39.ru
www.indfomed39.ru
www.inromed39.ru
www.infromed39.ru
www.inrfomed39.ru
www.intomed39.ru
www.inftomed39.ru
www.intfomed39.ru
www.ingomed39.ru
www.infgomed39.ru
www.ingfomed39.ru
www.invomed39.ru
www.infvomed39.ru
www.invfomed39.ru
www.infmed39.ru
www.infimed39.ru
www.infoimed39.ru
www.infiomed39.ru
www.infkmed39.ru
www.infokmed39.ru
www.infkomed39.ru
www.inflmed39.ru
www.infolmed39.ru
www.inflomed39.ru
www.infpmed39.ru
www.infopmed39.ru
www.infpomed39.ru
www.infoed39.ru
www.infoned39.ru
www.infomned39.ru
www.infonmed39.ru
www.infojed39.ru
www.infomjed39.ru
www.infojmed39.ru
www.infoked39.ru
www.infomked39.ru
www.infomd39.ru
www.infomwd39.ru
www.infomewd39.ru
www.infomwed39.ru
www.infomsd39.ru
www.infomesd39.ru
www.infomsed39.ru
www.infomdd39.ru
www.infomedd39.ru
www.infomded39.ru
www.infomrd39.ru
www.infomerd39.ru
www.infomred39.ru
www.infome39.ru
www.infomex39.ru
www.infomedx39.ru
www.infomexd39.ru
www.infomes39.ru
www.infomeds39.ru
www.infomee39.ru
www.infomede39.ru
www.infomeed39.ru
www.infomer39.ru
www.infomedr39.ru
www.infomef39.ru
www.infomedf39.ru
www.infomefd39.ru
www.infomec39.ru
www.infomedc39.ru
www.infomecd39.ru
www.infomed9.ru
www.infomed3.ru

infomed39.ru 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.


infomed39.ru 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.