NA24.NO Website Information

na24.no Website Information

Daily Unique Visits: 1,222

Daily Page Views: 2,444

Income Per Day: $8

Estimated Value: $1,920

This website is located in Norway and is using following IP address 185.57.253.180. See the complete list of popular websites hosted in Norway.

na24.no is registered under .NO top-level domain. Please check other sites in .NO zone.

Website na24.no is using the following name servers:

  • ns2.subsys.no
  • ns1.subsys.no
  • ns3.subsys.no

and is probably hosted by Nexthop AS. See the full list of other websites hosted by Nexthop AS.

The highest website na24.no position in Alexa rank database was 306824 and the lowest rank position was 998573. Current position of na24.no in Alexa rank database is 586772.

Desktop speed score of na24.no (13/100) shows that the page desktop performance can be improved.

Mobile usability score of na24.no (96/100) means that the page is mobile-friendly.

Mobile speed score of na24.no (42/100) shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

na24.no Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


na24.no whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


% By looking up information in the domain registration directory
% service, you confirm that you accept the terms and conditions of the
% service:
% https://www.norid.no/en/domeneoppslag/vilkar/
%
% Norid AS holds the copyright to the lookup service, content,
% layout and the underlying collections of information used in the
% service (cf. the Act on Intellectual Property of May 2, 1961, No.
% 2). Any commercial use of information from the service, including
% targeted marketing, is prohibited. Using information from the domain
% registration directory service in violation of the terms and
% conditions may result in legal prosecution.
%
% The whois service at port 43 is intended to contribute to resolving
% technical problems where individual domains threaten the
% functionality, security and stability of other domains or the
% internet as an infrastructure. It does not give any information
% about who the holder of a domain is. To find information about a
% domain holder, please visit our website:
% https://www.norid.no/en/domeneoppslag/

Domain Information

NORID Handle...............: NA52D-NORID
Domain Name................: na24.no
Registrar Handle...........: REG42-NORID
Tech-c Handle..............: DH38R-NORID
Name Server Handle.........: NSHY11H-NORID
Name Server Handle.........: NSHY46H-NORID
Name Server Handle.........: NSHY81H-NORID
DNSSEC.....................: Signed
DS Key Tag 1...........: 38224
Algorithm 1...........: 13
Digest Type 1...........: 2
Digest 1...........: 971b28a0e8c40fe4a131007dc3e1a6108d689315d8263846c2767d78987f3328
DS Key Tag 2...........: 38224
Algorithm 2...........: 13
Digest Type 2...........: 4
Digest 2...........: 184b866427cf539606984523271ce49ca49ad81703392e99523c9eca6ec282d177ecf3e6436944a26195239e58124270

Additional information:
Created: 2013-08-06
Last updated: 2021-07-10

na24.no server information

Servers Location

na24.no desktop page speed rank

Last tested: 2016-02-21


Desktop Speed Bad
13/100

na24.no Desktop Speed Test Quick Summary


priority - 397Optimize images

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

Optimize the following images to reduce their size by 3.8MiB (93% reduction).

Compressing and resizing http://drp-images.nettavisen.no/images/article/201…90/1/w1024/2496757.jpg could save 737.1KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…58/1/w1024/2409681.jpg could save 633.4KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…77/1/w1024/2451584.jpg could save 555.4KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…00/1/w1024/2436100.jpg could save 547.6KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…97/1/w1024/2421750.jpg could save 386.2KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…60/1/w1024/2139678.jpg could save 372.3KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…79/1/w1024/2512207.jpg could save 274.9KiB (98% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…ull-bredde/2508988.jpg could save 235.7KiB (95% reduction).
Compressing and resizing http://drp-images.nettavisen.no/images/article/201…69/1/w1024/2102600.jpg could save 109.9KiB (95% reduction).
Losslessly compressing http://fusion.nettavisen.no/1D02B672C/1D352EE96.jpg could save 1.6KiB (8% reduction).
Losslessly compressing https://www.google.com/cse/static/no/google_custom_search_watermark.gif could save 1.4KiB (69% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/header/seksjon_na24.png could save 1.3KiB (55% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/logo_na.png could save 1.1KiB (32% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/header/logo_nettavisen.png could save 1.1KiB (9% reduction).
Losslessly compressing http://pbx.images.nettavisen.no/?url=http://dingse…3&mode=crop&pos=center could save 1,022B (6% reduction).
Losslessly compressing http://s2.adform.net/Banners/13073940/13073940.jpg?bv=2 could save 921B (6% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/header/ikon_tjenester.png could save 910B (75% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/na24_android.jpg could save 904B (4% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/handlevogn_desktop.png could save 869B (85% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/stocklink_bors_knapp.jpg could save 847B (22% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/header/dropdownmenu_pil.png could save 846B (89% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/heade…lle_stripe_seksjon.jpg could save 842B (73% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/blogg_ikon_na24.png could save 842B (56% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/footer_fb.jpg could save 842B (8% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/na24_ipad.jpg could save 841B (3% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/na24_iphone.jpg could save 837B (4% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/na24/na24_logo.jpg could save 833B (12% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/vigne…n_bloggboble_small.png could save 772B (64% reduction).
Losslessly compressing http://pbx.images.nettavisen.no/?url=http://dingse…3&mode=crop&pos=center could save 630B (4% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/header/button_blogg.png could save 557B (24% reduction).
Losslessly compressing http://www.nettavisen.no/templates/v1/images/header/button_side3.png could save 521B (28% reduction).

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

Your page has 8 blocking script resources and 6 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.nettavisen.no/templates/v1/js/bundle.js?v1448623457000
http://www.nettavisen.no/templates/v1/js/jquery.webticker.js
http://www.nettavisen.no/templates/v1/js/na24/mbna.js?v=6
http://www.side2.no/templates/v1/js/df/mb.js?v14021
http://www.nettavisen.no/templates/v1/resources/advertisement-1.js
http://fusion.nettavisen.no/js/soxnu/mna.na24.na24…me=0917&weekDay=sunday
http://ad.360yield.com/adj?p=841635&w=1000&h=300&tz=480

Use asynchronous versions of the following scripts:

http://pagead2.googlesyndication.com/pagead/show_ads.js

Optimize CSS Delivery of the following:

http://fonts.googleapis.com/css?family=Open+Sans+Condensed:700
http://www.nettavisen.no/templates/v2/sass/css/section_na24.css?i=v0.005
http://www.nettavisen.no/templates/v1/css/header.css?i=5
http://nginx-drfront-api.nettavisen.no/nettavisen.…/front/40/css?i=v0.001
http://fonts.googleapis.com/css?family=Open+Sans:4…00italic,600,600italic
http://www.nettavisen.no/templates/v1/resources/ti…stylesheets/screen.css

priority - 19Leverage 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://cdn.adnxs.com/megatag.js (expiration not specified)
http://custom-joblist.s3.amazonaws.com/img/ajax-loader.gif (expiration not specified)
http://custom-joblist.s3.amazonaws.com/nettavisen.css (expiration not specified)
http://fusion.nettavisen.no/1CEDAD457/1D0F388DD.jpg (expiration not specified)
http://fusion.nettavisen.no/1D02B672C/1D352EE96.jpg (expiration not specified)
http://na.tns-cs.net/blank.gif (expiration not specified)
http://nginx-drfront-api.nettavisen.no/nettavisen.…/front/40/css?i=v0.001 (60 seconds)
http://s2.adform.net/stoat/570/s2.adform.net/boot.js (4.6 minutes)
http://www.nettavisen.no/templates/v1/images/handlevogn_desktop.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/button_blogg.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/button_side2.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/button_side3.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/dropdownmenu_pil.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/ikon_tjenester.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/logo_nettavisen.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/header/seksjon_na24.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/heade…lle_stripe_seksjon.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/highs…ines/rounded-white.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/logo_na.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/blogg_ikon_na24.png (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/footer_fb.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/na24_android.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/na24_ipad.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/na24_iphone.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/na24_logo.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/na24/stocklink_bors_knapp.jpg (10 minutes)
http://www.nettavisen.no/templates/v1/images/vigne…n_bloggboble_small.png (10 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-NHWDTG (16.2 minutes)
http://cdn.cxense.com/cx.js (60 minutes)
http://fusion.nettavisen.no/spl/x.js (60 minutes)
http://l.lp4.io/app/50/48/67/50486792d9d93ec413000000.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
http://s2.adform.net/Banners/13073940/13073940.jpg?bv=2 (60 minutes)
http://se-02.adtomafusion.com/spl/fif_scrpt.js (60 minutes)
https://js-agent.newrelic.com/nr-852.min.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)

priority - 7Avoid 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://na24.no/
http://www.na24.no/
http://www.nettavisen.no/na24/

priority - 4Enable 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 38.9KiB (73% reduction).

Compressing http://cdn.adnxs.com/megatag.js could save 30.8KiB (78% reduction).
Compressing http://ad.360yield.com/adj?p=825873&w=468&h=800&tz=480 could save 1.5KiB (58% reduction).
Compressing http://ad.360yield.com/ul_cb/adj?p=826995&w=160&h=600&tz=480 could save 1.5KiB (58% reduction).
Compressing http://ib.adnxs.com/mtj?id=1358123&mtjtag0=adnxs_t…=3&placements_loaded=1 could save 1.5KiB (56% reduction).
Compressing http://ib.adnxs.com/mtj?id=4122810&mtjtag0=adnxs_t…=3&placements_loaded=1 could save 1.5KiB (56% reduction).
Compressing http://ib.adnxs.com/mtj?id=5725654&mtjtag0=adnxs_t…=3&placements_loaded=1 could save 1.5KiB (56% reduction).
Compressing http://custom-joblist.s3.amazonaws.com/nettavisen.css could save 666B (68% reduction).

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

Minifying http://cdn.adnxs.com/megatag.js could save 7.5KiB (20% reduction).
Minifying http://www.nettavisen.no/templates/v1/js/bundle.js?v1448623457000 could save 6KiB (9% reduction) after compression.
Minifying http://www.nettavisen.no/templates/v1/js/jquery.webticker.js could save 1.2KiB (37% reduction) after compression.
Minifying http://pagead2.googlesyndication.com/pagead/js/r20…51006/show_ads_impl.js could save 713B (1% reduction) after compression.
Minifying https://pagead2.googlesyndication.com/pagead/js/r2…006/expansion_embed.js could save 536B (2% reduction) after compression.

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

Minifying http://www.nettavisen.no/na24/ could save 1.5KiB (6% reduction) after compression.
Minifying https://cdn.jobylon.com/jobs/company-groups/8/embe…al=5000&category_ids=6 could save 568B (10% reduction) after compression.

priority - 0Minify 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 537B (6% reduction).

Minifying http://nginx-drfront-api.nettavisen.no/nettavisen.…/front/40/css?i=v0.001 could save 537B (6% reduction) after compression.

na24.no Desktop Resource Breakdown

Total Resources222
Number of Hosts47
Static Resources155
JavaScript Resources49
CSS Resources13

na24.no mobile page speed rank

Last tested: 2019-12-25


Mobile Speed Bad
42/100

na24.no Mobile Speed Test Quick Summary


priority - 77Avoid landing page redirects

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

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

http://na24.no/
http://www.na24.no/
http://m.na24.no/
http://www.nettavisen.no/na24/
http://m.nettavisen.no/na24/

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

Your page has 7 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://m.nettavisen.no/templates/v1/js/bundle.js?v1.0
http://www.nettavisen.no/templates/v1/resources/advertisement-1.js
http://www.side2.no/templates/v1/js/df/mb.js?v050614
http://fusion.nettavisen.no/script.js?ads=na
http://m.nettavisen.no/templates/v1/js/fusion_utils_na_v2.js?v1444374854000
http://fusion.nettavisen.no/js/zysxn/mna.na24.mobi…me=0917&weekDay=sunday

Use asynchronous versions of the following scripts:

https://apis.google.com/js/plusone.js

Optimize CSS Delivery of the following:

http://m.nettavisen.no/templates/v2/sass/m/css/main.css?i=v0.002
http://nginx-drfront-api.nettavisen.no/nettavisen.…/front/40/css?i=v0.003
http://fonts.googleapis.com/css?family=Open+Sans:4…00italic,600,600italic
http://m.nettavisen.no/templates/v1/resources/tips…stylesheets/screen.css

priority - 16Leverage 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://custom-joblist.s3.amazonaws.com/img/ajax-loader.gif (expiration not specified)
http://custom-joblist.s3.amazonaws.com/nettavisen.css (expiration not specified)
http://na.tns-cs.net/blank.gif (expiration not specified)
http://nginx-drfront-api.nettavisen.no/nettavisen.…/front/40/css?i=v0.003 (60 seconds)
http://m.nettavisen.no/templates/v1/images/handlevogn_desktop.png (10 minutes)
http://m.nettavisen.no/templates/v1/images/highsli…ines/rounded-white.png (10 minutes)
http://m.nettavisen.no/templates/v1/images/m/blogg_ikon_mobile.png (10 minutes)
http://m.nettavisen.no/templates/v1/images/m/button_tiltoppen.jpg (10 minutes)
http://m.nettavisen.no/templates/v1/images/m/mobil_NA_logo.png (10 minutes)
http://m.nettavisen.no/templates/v1/images/m/mobil_ikon_meny.png (10 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
http://cdn.cxense.com/cx.js (60 minutes)
http://fusion.nettavisen.no/script.js?ads=na (60 minutes)
http://fusion.nettavisen.no/spl/x.js (60 minutes)
http://l.lp4.io/app/50/48/67/50486792d9d93ec413000000.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
http://se-02.adtomafusion.com/spl/fif_scrpt.js (60 minutes)
https://js-agent.newrelic.com/nr-852.min.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 2Enable 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 17.4KiB (62% reduction).

Compressing http://engine.widespace.com/map/engine/dynamic?sid…47c0-81dd-9401f6acecad could save 5.6KiB (62% reduction).
Compressing http://engine.widespace.com/map/engine/dynamic?sid…4db3-b667-8dfebe2e985d could save 5.6KiB (62% reduction).
Compressing http://engine.widespace.com/map/engine/dynamic?sid…4032-82da-a0288bb4d51c could save 5.6KiB (62% reduction).
Compressing http://custom-joblist.s3.amazonaws.com/nettavisen.css could save 666B (68% reduction).

priority - 2Minify 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 15.1KiB (6% reduction).

Minifying http://m.nettavisen.no/templates/v1/js/bundle.js?v1.0 could save 6KiB (9% reduction) after compression.
Minifying http://fusion.nettavisen.no/script.js?ads=na could save 4.5KiB (24% reduction) after compression.
Minifying http://m.nettavisen.no/templates/v2/js/bundle_bott…ront.js?v1452006862000 could save 2.5KiB (10% reduction) after compression.
Minifying http://m.nettavisen.no/templates/v1/js/fileInputCloak_snippet.js could save 791B (48% reduction) after compression.
Minifying http://pagead2.googlesyndication.com/pagead/js/r20…51006/show_ads_impl.js could save 714B (1% reduction) after compression.
Minifying https://pagead2.googlesyndication.com/pagead/js/r2…06/creative_toolset.js could save 536B (2% reduction) after compression.

priority - 1Optimize images

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

Optimize the following images to reduce their size by 6KiB (15% reduction).

Losslessly compressing http://m.nettavisen.no/templates/v1/images/m/mobil_NA_logo.png could save 1.4KiB (24% reduction).
Losslessly compressing http://m.nettavisen.no/templates/v1/images/m/mobil_ikon_meny.png could save 877B (88% reduction).
Losslessly compressing http://m.nettavisen.no/templates/v1/images/handlevogn_desktop.png could save 869B (85% reduction).
Losslessly compressing https://tpc.googlesyndication.com/simgad/2612850572046928324 could save 846B (5% reduction).
Losslessly compressing http://m.nettavisen.no/templates/v1/images/m/button_tiltoppen.jpg could save 841B (15% reduction).
Losslessly compressing http://m.nettavisen.no/templates/v1/images/m/blogg_ikon_mobile.png could save 732B (48% reduction).
Losslessly compressing http://pbx.images.nettavisen.no/?url=http://dingse…6&mode=crop&pos=center could save 566B (9% reduction).

priority - 0Minify 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.3KiB (6% reduction).

Minifying http://m.nettavisen.no/na24/ could save 718B (5% reduction) after compression.
Minifying https://cdn.jobylon.com/jobs/company-groups/8/embe…al=5000&category_ids=3 could save 573B (10% reduction) after compression.

priority - 0Minify 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 537B (6% reduction).

Minifying http://nginx-drfront-api.nettavisen.no/nettavisen.…/front/40/css?i=v0.003 could save 537B (6% reduction) after compression.

na24.no Mobile Resource Breakdown

Total Resources190
Number of Hosts41
Static Resources131
JavaScript Resources48
CSS Resources9

na24.no mobile page usability

Last tested: 2019-12-25


Mobile Usability Good
96/100

na24.no Mobile Usability Test Quick Summary


priority - 3Configure the viewport

Your page specifies a fixed-width mobile viewport. Consider using a responsive viewport to allow your page to render properly on all devices.

priority - 0Size 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 <div id="abgc" class="abgc">Annonsevalg</div> is close to 2 other tap targets.
The tap target <div id="abgc" class="abgc">Annonsevalg</div> is close to 2 other tap targets.
The tap target <a href="mailto:nettred…@nettavisen.no">Gunnar Stavrum</a> and 5 others are close to other tap targets.

na24.no HTML validation

na24.no similar domains

Similar domains:
www.na24.com
www.na24.net
www.na24.org
www.na24.info
www.na24.biz
www.na24.us
www.na24.mobi
www.a24.no
www.na24.no
www.ba24.no
www.nba24.no
www.bna24.no
www.ha24.no
www.nha24.no
www.hna24.no
www.ja24.no
www.nja24.no
www.jna24.no
www.ma24.no
www.nma24.no
www.mna24.no
www.n24.no
www.nq24.no
www.naq24.no
www.nqa24.no
www.nw24.no
www.naw24.no
www.nwa24.no
www.ns24.no
www.nas24.no
www.nsa24.no
www.nz24.no
www.naz24.no
www.nza24.no
www.na4.no
www.na2.no

na24.no Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


na24.no TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.