planetwin365.com

choose language: Current winnings played 650.00 € 25/06/2013 won 825.50 € EUR f.a. monte san biagio Bet Now! Why is PlanetWin365 better than the rest? Like what you see? Come join us! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 25-06-2013 11:49:28  (update).

Overview Info

  • Domain Name
    planetwin365.com
  • Favicon
  • Alexa Rank
    #79226
  • Google Page Rank
    PR 2
  • Ip Address
    81.2.199.135
  • Page Size
    14.5 KB
  • Images
    0 GIF, 0 JPG, 7 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Title
    PlanetWin365
  • Meta Keyword
  • Meta Description
    choose language: Current winnings played 650.00 € 25/06/2013 won 825.50 € EUR f.a. monte san biagio Bet Now! Why is PlanetWin365 better than the rest? Like what you see? Come join us!

Technical Analysis



  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    81.2.199.135
  • Domain Age
    4 Years, 1 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from planetwin365.com.

HTML Analysis

  • cache-control: private
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.0
  • host: WEB-05
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • x-machine-name: WEB-05
  • p3p: CP="COR ADM DEVi"
  • date: Tue, 25 Jun 2013 23:49:24 GMT
  • content-length: 5594
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Tavarelli, Paolo Carlo
ATTN PLANETWIN365.COM
care of Network Solutions
PO Box 459
Drums, PA. US 18222


Domain Name: PLANETWIN365.COM



Administrative Contact, Technical Contact:
Tavarelli, Paolo Carlo email
Sks365 GmbH
ATTN PLANETWIN365.COM
care of Network Solutions
PO Box 459
Drums, PA 18222
US
570-708-8780


Record expires on 27-May-2013.
Record created on 07-Oct-2009.
Database last updated on 30-Sep-2012 12:50:12 EDT.

Domain servers in listed order:

NS76.WORLDNIC.COM 206.188.198.38
NS75.WORLDNIC.COM 205.178.190.38

DNS Analysis


DNS servers
ns75.worldnic.com [205.178.190.38]
ns76.worldnic.com [206.188.198.38]


DNS Records

Answer records
planetwin365.com MX
preference: 10
exchange: mail.isolutions.it
7200s
planetwin365.com SOA
server: NS75.WORLDNIC.COM
email: namehost@WORLDNIC.COM
serial: 113012411
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
7200s
planetwin365.com NS  ns75.worldnic.com 7200s
planetwin365.com TXT v=spf1 mx a:smtp.aruba.it ip4:195.217.60.32/27 ip4:193.128.122.0/24 ~all 7200s
planetwin365.com NS  ns76.worldnic.com 7200s
planetwin365.com A 81.2.199.135 3600s

Authority records

Additional records

IP 81.2.199.135 Analysis

  • Country Code
    CZ
  • Country Code3
    CZE
  • Country Name
    Czech Republic
  • City
    EU
  • Continent Code
    49°75' North
  • Latitude
    15.5.
  • Longitude
  • No whois ip data for 81.2.199.135

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 25 Errors
  • 30 Warnings
Ratio Text/Html
  • 0.5176905001678416
Message Error
  • Warning Line 47, Column 50: cannot generate system identifier for general entity "url"
    … <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB' …

    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 47, Column 50: general entity "url" not defined and no default entity
    … <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB' …

    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 47, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'  ti…

    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 47, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'  ti…

    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 47, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 51, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=3&url=~/Sport/default.aspx" class='de-DE'  ti…

    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 51, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=3&url=~/Sport/default.aspx" class='de-DE'  ti…

    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 51, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=3&url=~/Sport/default.aspx" class='de-DE'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 55, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=1&url=~/Sport/default.aspx" class='it-IT'  ti…

    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 55, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=1&url=~/Sport/default.aspx" class='it-IT'  ti…

    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 55, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=1&url=~/Sport/default.aspx" class='it-IT'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 59, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=4&url=~/Sport/default.aspx" class='es-ES'  ti…

    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 59, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=4&url=~/Sport/default.aspx" class='es-ES'  ti…

    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 59, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=4&url=~/Sport/default.aspx" class='es-ES'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 63, Column 54: reference not terminated by REFC delimiter
    …href="../ChooseLanguage.aspx?ID=11&url=~/Sport/default.aspx" class='fr-FR'  ti…

    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 63, Column 54: reference to external entity in attribute value
    …href="../ChooseLanguage.aspx?ID=11&url=~/Sport/default.aspx" class='fr-FR'  ti…

    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 63, Column 54: reference to entity "url" for which no system identifier could be generated
    …href="../ChooseLanguage.aspx?ID=11&url=~/Sport/default.aspx" class='fr-FR'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 67, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=5&url=~/Sport/default.aspx" class='sr-Latn-CS…

    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 67, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=5&url=~/Sport/default.aspx" class='sr-Latn-CS…

    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 67, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=5&url=~/Sport/default.aspx" class='sr-Latn-CS…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 71, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=7&url=~/Sport/default.aspx" class='bg-BG'  ti…

    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 71, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=7&url=~/Sport/default.aspx" class='bg-BG'  ti…

    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 71, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=7&url=~/Sport/default.aspx" class='bg-BG'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 75, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=6&url=~/Sport/default.aspx" class='pl-PL'  ti…

    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 75, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=6&url=~/Sport/default.aspx" class='pl-PL'  ti…

    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 75, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=6&url=~/Sport/default.aspx" class='pl-PL'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 79, Column 54: reference not terminated by REFC delimiter
    …href="../ChooseLanguage.aspx?ID=14&url=~/Sport/default.aspx" class='es-PE'  ti…

    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 79, Column 54: reference to external entity in attribute value
    …href="../ChooseLanguage.aspx?ID=14&url=~/Sport/default.aspx" class='es-PE'  ti…

    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 79, Column 54: reference to entity "url" for which no system identifier could be generated
    …href="../ChooseLanguage.aspx?ID=14&url=~/Sport/default.aspx" class='es-PE'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 83, Column 54: reference not terminated by REFC delimiter
    …href="../ChooseLanguage.aspx?ID=15&url=~/Sport/default.aspx" class='es-EC'  ti…

    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 83, Column 54: reference to external entity in attribute value
    …href="../ChooseLanguage.aspx?ID=15&url=~/Sport/default.aspx" class='es-EC'  ti…

    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 83, Column 54: reference to entity "url" for which no system identifier could be generated
    …href="../ChooseLanguage.aspx?ID=15&url=~/Sport/default.aspx" class='es-EC'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 87, Column 53: reference not terminated by REFC delimiter
    … href="../ChooseLanguage.aspx?ID=9&url=~/Sport/default.aspx" class='tr-TR'  ti…

    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 87, Column 53: reference to external entity in attribute value
    … href="../ChooseLanguage.aspx?ID=9&url=~/Sport/default.aspx" class='tr-TR'  ti…

    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 87, Column 53: reference to entity "url" for which no system identifier could be generated
    … href="../ChooseLanguage.aspx?ID=9&url=~/Sport/default.aspx" class='tr-TR'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 91, Column 54: reference not terminated by REFC delimiter
    …href="../ChooseLanguage.aspx?ID=10&url=~/Sport/default.aspx" class='sq-AL'  ti…

    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 91, Column 54: reference to external entity in attribute value
    …href="../ChooseLanguage.aspx?ID=10&url=~/Sport/default.aspx" class='sq-AL'  ti…

    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 91, Column 54: reference to entity "url" for which no system identifier could be generated
    …href="../ChooseLanguage.aspx?ID=10&url=~/Sport/default.aspx" class='sq-AL'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 95, Column 54: reference not terminated by REFC delimiter
    …href="../ChooseLanguage.aspx?ID=16&url=~/Sport/default.aspx" class='ro-RO'  ti…

    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 95, Column 54: reference to external entity in attribute value
    …href="../ChooseLanguage.aspx?ID=16&url=~/Sport/default.aspx" class='ro-RO'  ti…

    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 95, Column 54: reference to entity "url" for which no system identifier could be generated
    …href="../ChooseLanguage.aspx?ID=16&url=~/Sport/default.aspx" class='ro-RO'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Warning Line 99, Column 54: reference not terminated by REFC delimiter
    …href="../ChooseLanguage.aspx?ID=17&url=~/Sport/default.aspx" class='de-AT'  ti…

    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 99, Column 54: reference to external entity in attribute value
    …href="../ChooseLanguage.aspx?ID=17&url=~/Sport/default.aspx" class='de-AT'  ti…

    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 99, Column 54: reference to entity "url" for which no system identifier could be generated
    …href="../ChooseLanguage.aspx?ID=17&url=~/Sport/default.aspx" class='de-AT'  ti…

    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 47, Column 49: entity was defined here
    …  <a href="../ChooseLanguage.aspx?ID=2&url=~/Sport/default.aspx" class='en-GB'…
  • Error Line 131, Column 25: 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 279, Column 55: required attribute "alt" not specified
    								<img src="/ImgCMS/LandingPage/happyhour.png" />

    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 286, Column 58: required attribute "alt" not specified
    								<img src="/ImgCMS/LandingPage/portomaso_IT.png" />

    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 297, Column 58: required attribute "alt" not specified
    										<img src="/ImgCMS/LandingPage/VS_moto_IT.png" />

    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 302, Column 59: required attribute "alt" not specified
    										<img src="/ImgCMS/LandingPage/VS_horse_IT.png" />

    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 307, Column 60: required attribute "alt" not specified
    										<img src="/ImgCMS/LandingPage/VS_soccer_IT.png" />

    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 314, Column 57: required attribute "alt" not specified
    						<img src="/ImgCMS/LandingPage/cartecredito3.png" />

    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 316, Column 93: required attribute "alt" not specified
    …r="0" src="/ImgCMS/LandingPage/carteCredito2.png" usemap="#carteCredito_Map" />

    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 318, Column 33: required attribute "id" not specified
    				<map name="carteCredito_Map">

    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 324, Column 73: required attribute "alt" not specified
    				<img border="0" src="/ImgCMS/partners5.jpg" usemap="#partners_Map" />

    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 325, Column 29: required attribute "id" not specified
    				<map name="partners_Map">

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

Visitor Analysis

Daily Visitor
  • 1.377 visits
Daily Visitor

In Page Analysis