Switch to mobile version Helpdesk 8002 8004Helpdesk 8002 8004Helpdesk 8002 8004 Mo–So: 0000–2400Mo–Su: 0000–2400Lu–Di: 0000–2400 Webmail LoginWebmail LoginWebmail Login BenutzernameUsernameNom d'utilisateur KennwortPasswordMot de passe SpracheLanguag ... ...

webmail.pt.lu
  • Domain Name
    webmail.pt.lu
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #33074
  • Page Size
    10.1 KB
  • Ip Address
    195.46.255.229
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 0 JPG, 0 PNG

Website Meta Analysis

  • Title
    POST Luxembourg
  • Meta Keyword
  • Meta Description
    Switch to mobile version Helpdesk 8002 8004Helpdesk 8002 8004Helpdesk 8002 8004 Mo–So: 0000–2400Mo–Su: 0000–2400Lu–Di: 0000–2400 Webmail LoginWebmail LoginWebmail Login BenutzernameUsernameNom d'utilisateur KennwortPasswordMot de passe SpracheLanguag ...

Technical Analysis

  • Webserver
    Apache/2.2.3 (Red Hat)
  • Ip Address
    195.46.255.229
  • Domain Age
  • Javascript Library
    prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from webmail.pt.lu.

HTML Analysis

  • date: Tue, 12 Nov 2013 19:30:41 GMT
  • server: Apache/2.2.3 (Red Hat)
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for webmail.pt.lu

IP 195.46.255.229 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 195.46.255.229

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 12 Errors
  • 13 Warnings
Ratio Text/Html
  • 0.7655145706263917
Message Error
  • Warning Line 86, Column 53: cannot generate system identifier for general entity "isxhtml"
    …://m.pt.lu/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to m…

    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 "&" (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 æ 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 86, Column 53: general entity "isxhtml" not defined and no default entity
    …://m.pt.lu/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to m…

    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 86, Column 60: reference not terminated by REFC delimiter
    ….lu/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile v…

    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 86, Column 60: reference to external entity in attribute value
    ….lu/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile v…

    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 '&'.

  • Error Line 86, Column 60: reference to entity "isxhtml" for which no system identifier could be generated
    ….lu/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile v…

    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 86, Column 52: entity was defined here
    …s://m.pt.lu/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to …
  • Warning Line 86, Column 63: cannot generate system identifier for general entity "todo"
    …/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile vers…

    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 "&" (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 æ 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 86, Column 63: general entity "todo" not defined and no default entity
    …/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile vers…

    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 86, Column 67: reference not terminated by REFC delimiter
    …mail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile version<…

    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 86, Column 67: reference to external entity in attribute value
    …mail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile version<…

    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 86, Column 67: reference to entity "todo" for which no system identifier could be generated
    …mail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile version<…

    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 86, Column 62: entity was defined here
    …u/webmail/index?device=xhtml&isxhtml=1&todo=deviceswitch">Switch to mobile ver…
  • Error Line 92, Column 67: required attribute "alt" not specified
      <img src="/img.webmail/ptlu/img-logowebmail.png" id="headimg1" />

    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 94, Column 60: required attribute "alt" not specified
      <img src="/img.webmail/ptlu/pt_logo.png"  id="headimg2" />

    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 141, Column 65: there is no attribute "TABINDEX"
    <select name="lang" onchange="setLanguage(this.value)" TABINDEX="4">

    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 143, Column 30: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
      <option value="en" selected>English</option>

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Warning Line 154, Column 93: cannot generate system identifier for general entity "T"
    …display:none">© 2010 Entreprise des P&T</span><span class="en" style="display:…

    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 154, Column 93: general entity "T" not defined and no default entity
    …display:none">© 2010 Entreprise des P&T</span><span class="en" style="display:…

    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 154, Column 94: reference not terminated by REFC delimiter
    …isplay:none">© 2010 Entreprise des P&T</span><span class="en" style="display:n…

    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 154, Column 94: reference to entity "T" for which no system identifier could be generated
    …isplay:none">© 2010 Entreprise des P&T</span><span class="en" style="display:n…

    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 154, Column 92: entity was defined here
    …"display:none">© 2010 Entreprise des P&T</span><span class="en" style="display…
  • Warning Line 154, Column 164: reference not terminated by REFC delimiter
    …isplay:none">© 2010 Entreprise des P&T</span><span class="fr" style="display:n…

    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 154, Column 164: reference to entity "T" for which no system identifier could be generated
    …isplay:none">© 2010 Entreprise des P&T</span><span class="fr" style="display:n…

    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 154, Column 92: entity was defined here
    …"display:none">© 2010 Entreprise des P&T</span><span class="en" style="display…
  • Warning Line 154, Column 234: reference not terminated by REFC delimiter
    …</span><span class="fr" style="display:none">© 2010 Entreprise des P&T</span> |

    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 154, Column 234: reference to entity "T" for which no system identifier could be generated
    …</span><span class="fr" style="display:none">© 2010 Entreprise des P&T</span> |

    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 154, Column 92: entity was defined here
    …"display:none">© 2010 Entreprise des P&T</span><span class="en" style="display…
  • Warning Line 137, Column 25: reference to non-existent ID "password"
                <label for="password"><span class="de" style="display:none">Kennwor…

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

  • Warning Line 140, Column 25: reference to non-existent ID "lang"
                <label for="lang"><span class="de" style="display:none">Sprache</sp…

    This error can be triggered by:

    • A non-existent input, select or textarea element
    • A missing id attribute
    • A typographical error in the id attribute

    Try to check the spelling and case of the id you are referring to.

Visitor Analysis

Daily Visitor
  • 3.267 visits