112.be Website Information
Daily Unique Visits: 2,530
Daily Page Views: 7,590
Income Per Day: $23
Estimated Value: $8,280
112.be is registered under .BE top-level domain. Please check other sites in .BE zone.
No name server records were found.
and is probably hosted by BELNET. See the full list of other websites hosted by BELNET.
The highest website 112.be position in Alexa rank database was 46773 and the lowest rank position was 989868. Current position of 112.be in Alexa rank database is 425215.
Desktop speed score of 112.be (75/100) is better than the results of 59.78% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of 112.be (69/100) is better than the results of 20.4% of other sites and means that the page is not mobile-friendly.
Mobile speed score of 112.be (62/100) is better than the results of 59.44% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
112.be 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.
112.be 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.
%
% The WHOIS service offered by DNS Belgium and the access to the records in the DNS Belgium
% WHOIS database are provided for information purposes only. It allows
% persons 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.
%
% DNS Belgium cannot, under any circumstances, be held liable where the stored
% information would prove to be incomplete or inaccurate in any sense.
%
% By submitting a query you agree not to use the information made available
% to:
% - allow, enable or otherwise support the transmission of unsolicited,
% commercial advertising or other solicitations whether via email or otherwise;
% - target advertising in any possible way;
% - to cause nuisance in any possible way to the domain name holders by sending
% messages to them (whether by automated, electronic processes capable of
% enabling high volumes or other possible means).
%
% Without prejudice to the above, it is explicitly forbidden to extract, copy
% and/or use or re-utilise 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 DNS Belgium, nor in any attempt thereof, to apply automated, electronic
% processes to DNS Belgium (or its 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 submitting the query you agree to abide by this policy and accept that
% DNS Belgium 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.
%
Domain: 112.be
Status: NOT AVAILABLE
Registered: Wed Dec 13 2000
Registrant:
Not shown, please visit www.dnsbelgium.be for webbased whois.
Registrar Technical Contacts:
Organisation: Kanselarij van de Eerste Minister Chancellerie du Premier Ministre
Language: nl
Phone: +32.25010555
Registrar:
Name: Kanselarij van de Eerste Minister - Externe Communicatie Chancellerie du Premier Ministre - Communication Externe
Website: http://www.belgium.be
Nameservers:
europe1.dnsnode.net
nsp.dnsnode.net
nsu.dnsnode.net
Keys:
keyTag:31516 flags:KSK protocol:3 algorithm:RSA-SHA256 pubKey:AwEAAfkIAxcT2qZyYhvpRDzcb4UHFWi14dvwHs0q5Pv+BM/XAT1nn+3WPDCEHkPH/0DwBkaxxcU4xuW5vFWaoka9T8kznxB9Q0NlZM1DLgTFzNWdXArgQhk3GPpG8ovSLweMOgshuTZgphFfUpcSlou1uX6P3kUGdTlFV3XeNgQiPQV134IfwnlZc5n7J2B88HN53bzEUE0YdvtTTf7+3pzuJvlV7qmNTDff9SwhENOyDGEs+NO5o4BdCtAZUaBSgyWf/y14LNq5RHZLYgHRrqrOtkH9FZQe/IS/HPc8nWknA2sC83JXdQmNuDp0VHws/KDZLnRCo76Otch/IJNr0IHogRE=
Flags:
clientTransferProhibited
Please visit www.dnsbelgium.be for more info.
112.be server information
Servers Location
112.be desktop page speed rank
Last tested: 2018-07-12
112.be Desktop Speed Test Quick Summary
priority - 11Enable 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 109.4KiB (66% reduction).
Compressing https://112.be/js/jquery.cycle.js could save 19.2KiB (71% reduction).
Compressing https://112.be/js/fancybox/jquery.fancybox.pack.js?v=2.1.5 could save 14.2KiB (62% reduction).
Compressing https://112.be/css/style.css could save 12.2KiB (77% reduction).
Compressing https://112.be/js/fancybox/jquery.fancybox.css?v=2.1.5 could save 3.4KiB (70% reduction).
Compressing https://112.be/js/script.js could save 1.2KiB (62% reduction).
priority - 10Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://112.be/js/jquery.cycle.js
https://112.be/js/fancybox/jquery.fancybox.pack.js?v=2.1.5
https://112.be/js/script.js
https://112.be/js/twitter.js
Optimize CSS Delivery of the following:
https://112.be/css/style.css
https://112.be/js/fancybox/jquery.fancybox.css?v=2.1.5
priority - 7Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 72.6KiB (46% reduction).
Compressing https://112.be/images/bgr_top.jpg could save 8.8KiB (44% reduction).
Compressing https://112.be/images/puc_friend1.png could save 2.5KiB (16% reduction).
Compressing and resizing https://112.be/images/ico-fb.png could save 2.1KiB (83% reduction).
Compressing https://112.be/images/puc_friend5.png could save 1.8KiB (21% reduction).
Compressing https://112.be/images/logo.png could save 1.8KiB (23% reduction).
Compressing https://112.be/images/puc_friend3.png could save 1.6KiB (15% reduction).
Compressing https://112.be/images/puc_friend2.png could save 1.4KiB (20% reduction).
Compressing https://112.be/images/bgr_body.png could save 1.2KiB (43% reduction).
Compressing https://112.be/images/bgr_side_bar_title.png could save 1.2KiB (40% reduction).
Compressing https://112.be/images/puc_friend6.png could save 1.1KiB (31% reduction).
Compressing https://112.be/images/bgr_header.png could save 906B (88% reduction).
Compressing https://112.be/images/bgr_side_bar_top.png could save 871B (73% reduction).
Compressing https://112.be/images/bgr_language_hover.png could save 862B (85% reduction).
Compressing https://112.be/images/bgr_menu_divider.png could save 855B (91% reduction).
Compressing https://112.be/images/bgr_menu_hover.png could save 853B (92% reduction).
Compressing https://112.be/images/bgr_side_bar.png could save 851B (89% reduction).
Compressing https://112.be/images/bgr_service_note.png could save 767B (52% reduction).
Compressing https://112.be/images/bgr_side_bar_bottom.png could save 762B (55% reduction).
Compressing https://112.be/images/bgr_service_note_arrow_mobility.png could save 685B (47% reduction).
Compressing https://112.be/images/bgr_service_note_arrow_number.png could save 677B (47% reduction).
Compressing https://112.be/images/bgr_service_note_arrow_available.png could save 641B (41% reduction).
Compressing https://112.be/images/puc_friend4.png could save 613B (12% reduction).
priority - 3Leverage 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://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/nl_NL/all.js (20 minutes)
https://connect.facebook.net/signals/config/155668…5903?v=2.8.20&r=stable (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
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 2.7KiB (13% reduction).
Minifying https://112.be/js/fancybox/jquery.fancybox.css?v=2.1.5 could save 942B (20% reduction).
priority - 0Minify 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 344B (19% reduction).
112.be Desktop Resource Breakdown
Total Resources | 67 |
Number of Hosts | 12 |
Static Resources | 50 |
JavaScript Resources | 14 |
CSS Resources | 3 |
112.be mobile page speed rank
Last tested: 2018-06-14
112.be Mobile Speed Test Quick Summary
priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 5 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://112.be/js/jquery.cycle.js
https://112.be/js/fancybox/jquery.fancybox.pack.js?v=2.1.5
https://112.be/js/script.js
https://112.be/js/twitter.js
Optimize CSS Delivery of the following:
https://112.be/css/style.css
https://112.be/js/fancybox/jquery.fancybox.css?v=2.1.5
priority - 11Enable 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 109.4KiB (66% reduction).
Compressing https://112.be/js/jquery.cycle.js could save 19.2KiB (71% reduction).
Compressing https://112.be/js/fancybox/jquery.fancybox.pack.js?v=2.1.5 could save 14.2KiB (62% reduction).
Compressing https://112.be/css/style.css could save 12.2KiB (77% reduction).
Compressing https://112.be/js/fancybox/jquery.fancybox.css?v=2.1.5 could save 3.4KiB (70% reduction).
Compressing https://112.be/js/script.js could save 1.2KiB (62% reduction).
priority - 7Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 71.4KiB (45% reduction).
Compressing https://112.be/images/bgr_top.jpg could save 8.8KiB (44% reduction).
Compressing https://112.be/images/puc_friend1.png could save 2.5KiB (16% reduction).
Compressing https://112.be/images/puc_friend5.png could save 1.8KiB (21% reduction).
Compressing https://112.be/images/logo.png could save 1.8KiB (23% reduction).
Compressing https://112.be/images/puc_friend3.png could save 1.6KiB (15% reduction).
Compressing https://112.be/images/puc_friend2.png could save 1.4KiB (20% reduction).
Compressing https://112.be/images/bgr_body.png could save 1.2KiB (43% reduction).
Compressing https://112.be/images/bgr_side_bar_title.png could save 1.2KiB (40% reduction).
Compressing https://112.be/images/puc_friend6.png could save 1.1KiB (31% reduction).
Compressing https://112.be/images/bgr_header.png could save 906B (88% reduction).
Compressing https://112.be/images/ico-fb.png could save 887B (35% reduction).
Compressing https://112.be/images/bgr_side_bar_top.png could save 871B (73% reduction).
Compressing https://112.be/images/bgr_language_hover.png could save 862B (85% reduction).
Compressing https://112.be/images/bgr_menu_divider.png could save 855B (91% reduction).
Compressing https://112.be/images/bgr_menu_hover.png could save 853B (92% reduction).
Compressing https://112.be/images/bgr_side_bar.png could save 851B (89% reduction).
Compressing https://112.be/images/bgr_service_note.png could save 767B (52% reduction).
Compressing https://112.be/images/bgr_side_bar_bottom.png could save 762B (55% reduction).
Compressing https://112.be/images/bgr_service_note_arrow_mobility.png could save 685B (47% reduction).
Compressing https://112.be/images/bgr_service_note_arrow_number.png could save 677B (47% reduction).
Compressing https://112.be/images/bgr_service_note_arrow_available.png could save 641B (41% reduction).
Compressing https://112.be/images/puc_friend4.png could save 613B (12% reduction).
priority - 4Leverage 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://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/nl_NL/all.js (20 minutes)
https://connect.facebook.net/signals/config/155668…5903?v=2.8.16&r=stable (20 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://ssl.google-analytics.com/ga.js (2 hours)
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 2.7KiB (13% reduction).
Minifying https://112.be/js/fancybox/jquery.fancybox.css?v=2.1.5 could save 942B (20% reduction).
priority - 0Minify 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 344B (19% reduction).
112.be Mobile Resource Breakdown
Total Resources | 67 |
Number of Hosts | 12 |
Static Resources | 50 |
JavaScript Resources | 14 |
CSS Resources | 3 |
112.be mobile page usability
Last tested: 2018-06-14
112.be Mobile Usability Test Quick Summary
priority - 25Use legible font sizes
The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.
The following text fragments have a small font size. Increase the font size to make them more legible.
NL
renders only 5 pixels tall (13 CSS pixels).FR
and 2 others render only 5 pixels tall (13 CSS pixels).Volg onze oper…s via facebook
and 1 others render only 5 pixels tall (14 CSS pixels).Home
renders only 7 pixels tall (19 CSS pixels).dringend?
and 16 others render only 7 pixels tall (19 CSS pixels).is het enige n…of de politie.
and 1 others render only 8 pixels tall (20 CSS pixels).“112”
renders only 8 pixels tall (20 CSS pixels).Als je in Belg…101 te bellen.
renders only 5 pixels tall (14 CSS pixels).AMBULANCE, BRA…EN/OF POLITIE
and 2 others render only 8 pixels tall (20 CSS pixels).Het belangrijk…je nodig hebt.
and 2 others render only 5 pixels tall (14 CSS pixels).Lees meer
renders only 5 pixels tall (14 CSS pixels).zijn, maar bij…rmatie, om een
and 10 others render only 5 pixels tall (14 CSS pixels).van een vaste,…betaaltelefoon
and 7 others render only 5 pixels tall (14 CSS pixels).Vind ik leuk
renders only 4 pixels tall (11 CSS pixels).131
renders only 4 pixels tall (11 CSS pixels).Tweet
renders only 4 pixels tall (11 CSS pixels).Copyright © 20…tiatief van de
and 1 others render only 5 pixels tall (12 CSS pixels).priority - 10Configure the viewport
Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.
priority - 6Size 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="/nl/">nl</a>
is close to 2 other tap targets.<a href="/fr/">fr</a>
and 2 others are close to other tap targets.<a href="https://www.fa…k.com/sos112be">Volg onze oper…s via facebook</a>
and 1 others are close to other tap targets.<a href="/nl/">Home</a>
is close to 1 other tap targets.<a href="/nl/">Home</a>
is close to 1 other tap targets.<a href="/nl/app">APP</a>
and 4 others are close to other tap targets.<a href="/nl/app">APP</a>
and 4 others are close to other tap targets.<a href="/nl/faq-112.html#7">Met één oproep…en/of politie</a>
is close to 1 other tap targets.<a href="/nl/faq-112.html">Je kan 24 uur…/7 beschikbaar</a>
is close to 1 other tap targets.<a href="/nl/faq-112.html">Je kan 24 uur…/7 beschikbaar</a>
is close to 1 other tap targets.<a href="https://www.112.be/nl/app">Lees meer</a>
is close to 1 other tap targets.<a id="b" href="https://twitte…2F%2F112.be%2F" class="btn">Tweet</a>
is close to 3 other tap targets.priority - 5Size content to viewport
The page content is too wide for the viewport, forcing the user to scroll horizontally. Size the page content to the viewport to provide a better user experience.
The page content is 990 CSS pixels wide, but the viewport is only 980 CSS pixels wide. The following elements fall outside the viewport:
<ul>nlfrdeen</ul>
falls outside the viewport.The element
<li class="last">Contact</li>
falls outside the viewport.The element
<div class="info">Het noodnummer…101 te bellen.</div>
falls outside the viewport.The element
<span class="note">24/7 beschikbaar</span>
falls outside the viewport.The element
<div class="top">
falls outside the viewport.The element
<h2>Wist je dàt ... ?</h2>
falls outside the viewport.The element
<div class="bottom">
falls outside the viewport.The element
<li></li>
falls outside the viewport.The element
<div class="footer_content">Volg onze oper…enlandse Zaken</div>
falls outside the viewport.112.be HTML validation
Errors
Obsolete doctype. Expected “<!DOCTYPE html>”.
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."
Bad value “https://fonts.googleapis.com/css?family=PT+Sans:400,700,400italic,700italic|PT+Sans+Narrow:400,700” for attribute “href” on element “link”: Illegal character in query: “|” is not allowed.
"...lgië." /> <link rel="stylesheet" type="text/css" href="https://fonts.googleapis.com/css?family=PT+Sans:400,700,400italic,700italic|PT+Sans+Narrow:400,700" /> <lin..."
Bad value “screen,projection” for attribute “media” on element “link”: Deprecated media type “projection”. For guidance, see the Media Types section in the current Media Queries specification.
"...,700" /> <link rel="stylesheet" type="text/css" media="screen,projection" href="/css/style.css" /> <lin..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"...<noscript><img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1556686974655903&ev=PageView&noscript=1" /></nosc..." Line: 69 Column: 150 - 269
"...="_blank"><img src="/uploads/SMS_APP112/infographie_metro-NL-112be-def-21-06-2017-petit.jpg" border="0" width="80" height="238" /></a>De..."
Warnings
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...="_blank"><img src="/uploads/SMS_APP112/infographie_metro-NL-112be-def-21-06-2017-petit.jpg" border="0" width="80" height="238" /></a>De..."
This document appears to be written in Dutch. Consider adding “lang="nl"” (or variant) to the “html” start tag.
"...rict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head..."
112.be similar domains
www.112.net
www.112.org
www.112.info
www.112.biz
www.112.us
www.112.mobi
www.12.be
www.112.be
www.11.be
112.be 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.
112.be 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.