vietteltelecom.vn has Alexa Rank 37.858 and Google Page Rank is 6

vietteltelecom.vn
  • Domain Name
    vietteltelecom.vn
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #37858
  • Page Size
    38 KB
  • Ip Address
    125.235.4.27
  • Heading
    H1: 0, H2: 0, H3: 3, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 13 JPG, 7 PNG

Website Meta Analysis

  • Title
    Trang chủ | Viettel Telecom Portal
  • Meta Keyword
  • Meta Description

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    125.235.4.27
  • Domain Age
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from vietteltelecom.vn.

HTML Analysis

  • server: Apache
  • x-powered-by: PHP/5.3.14
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-type: text/html; charset=utf-8
  • content-length: 7579
  • date: Sat, 09 Feb 2013 19:35:25 GMT
  • x-varnish: 933332641
  • via: 1.1 varnish
  • connection: keep-alive
  • age: 0
  • cache-control: no-cache
  • x-google-cache-control: remote-fetch
No data whois for vietteltelecom.vn

DNS Analysis


DNS servers
dns1.viettel.com.vn [203.113.131.1]
dns2.viettel.com.vn [203.113.188.2]
Query for DNS records for vietteltelecom.vn failed: Timed out

DNS Records

IP 125.235.4.27 Analysis

  • Country Code
    VN
  • Country Code3
    VNM
  • Country Name
    Vietnam
  • City
    Hanoi
  • Continent Code
    AS
  • Latitude
    21.0333
  • Longitude
    105.85
  • % [whois.apnic.net node-6]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 125.235.0.0 - 125.235.255.255
    netname: xDSLservices-net
    country: vn
    descr: xDSL Services of DaNang
    admin-c: NH186-AP
    tech-c: MGH3-AP
    status: ALLOCATED NON-PORTABLE
    changed: hm-changed@vnnic.net.vn 20100308
    mnt-by: MAINT-VN-VIETEL
    source: APNIC

    route: 125.234.0.0/15
    descr: Vietel Corporation
    descr: Internet service/exchange provider
    descr: VIETEL-AS-AP
    country: VN
    origin: AS7552
    member-of: rs-vietel
    remarks: mailto: noc@viettel.com.vn
    notify: hm-changed@vnnic.net.vn
    mnt-by: MAINT-VN-VIETEL
    changed: hm-changed@vnnic.net.vn 20060118
    source: APNIC

    person: Nguyen Hoang Chuong
    nic-hdl: NH186-AP
    e-mail: abuse@vietel.com.vn
    address: 47 Huynh Thuc Khang str, Dong Da, Ha Noi
    phone: +84-426-60078
    fax-no: +84-426-60096
    country: vn
    changed: hm-changed@vnnic.net.vn 20060403
    mnt-by: MAINT-VN-VIETEL
    source: APNIC

    person: Mai Gia Ha
    nic-hdl: MGH3-AP
    e-mail: noc@vietel.com.vn
    address: 01 Giang Van Minh, Ba Dinh, Ha Noi
    phone: +84-98-3000955
    fax-no: +84-426-60446
    country: vn
    changed: hm-changed@vnnic.net.vn 20121211
    mnt-by: MAINT-VN-VIETEL
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 21 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.7212903889689237
Message Error
  • Error Line 21, Column 80: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
      <input type="text" name="query" value=""	class="field"	id="search_keywords" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 22, Column 83: document type does not allow element "input" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "address", "fieldset" start-tag
    …nput type="submit" value="" id="iconsubmit" onclick="return validateQuery()" />

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  • Error Line 23, Column 9: end tag for "form" which is not finished
      </form>

    Most likely, you nested tags and closed them in the wrong order. For example <p><em>...</p> is not acceptable, as <em> must be closed before <p>. Acceptable nesting is: <p><em>...</em></p>

    Another possibility is that you used an element which requires a child element that you did not include. Hence the parent element is "not finished", not complete. For instance, in HTML the <head> element must contain a <title> child element, lists require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 36, Column 508: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 2900: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 3927: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 5276: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 6502: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 8693: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 36, Column 10380: required attribute "alt" not specified
    …p_76.png" style="margin-right:150px;"/><div class="r1f"></div><div class="r2f"…

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 119, Column 83: there is no attribute "target"
    …ietteltelecom.vn/video/4.html" target="_blank">Xem c&aacute;c Clip hay</a><br …

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 130, Column 18: reference not terminated by REFC delimiter
            <h3>&nbsp</h3>  	

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 166, Column 83: there is no attribute "empty_value"
    …="vtp_contact_form[body]" empty_value="Hãy nhập những ý kiến đóng góp của bạn …

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 169, Column 69: there is no attribute "empty_value"
    …"vtp_contact_form[email]" empty_value="Email" class="required" id="vtp_contact…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 174, Column 166: there is no attribute "onClick"
    …ct_form_captcha" /><a href='' onClick='return false' title='Reload image'><img…

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 174, Column 260: there is no attribute "onClick"
    …ge' src='/captcha?1360438528' onClick='this.src="/captcha?r=" + Math.random() …

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Warning Line 174, Column 304: cannot generate system identifier for general entity "reload"
    …src="/captcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' />…

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 174, Column 304: general entity "reload" not defined and no default entity
    …src="/captcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' />…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 174, Column 310: reference not terminated by REFC delimiter
    …captcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' /></a>		…

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 174, Column 310: reference to external entity in attribute value
    …captcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' /></a>		…

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 174, Column 310: reference to entity "reload" for which no system identifier could be generated
    …captcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' /></a>		…

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 174, Column 303: entity was defined here
    ….src="/captcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' /…
  • Error Line 174, Column 322: there is no attribute "border"
    …ptcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' /></a>					

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 174, Column 343: required attribute "alt" not specified
    …ptcha?r=" + Math.random() + "&reload=1"' border='0' class='captcha' /></a>					

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 252, Column 23: document type does not allow element "style" here
    <style type="text/css">

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 301, Column 86: end tag for "br" omitted, but OMITTAG NO was specified
    …Giấy phép số: 144/GP-BC do Bộ Thông tin - Truyền thông cấp ngày 18/04/2007 <br>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 301, Column 82: start tag was here
    …Giấy phép số: 144/GP-BC do Bộ Thông tin - Truyền thông cấp ngày 18/04/2007 <br>

Visitor Analysis

Daily Visitor
  • 5.717 visits
Daily Visitor