Formar parte del club de venta privada ofertix.com es totalmente gratuito y sin ningún compromiso. Ventas Exclusivas Primeras Marcas. Ofertix, The Shop Stock. Es un club de compra venta privada online que organiza, ...

ofertix.com
  • Domain Name
    ofertix.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #9633
  • Page Size
    13.6 KB
  • Ip Address
    91.223.61.17
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 7 JPG, 0 PNG

Website Meta Analysis

  • Title
    Ofertix | Club de Venta Privada
  • Meta Keyword
    Ofertix, Club de Venta Privada, Club Venta Privada, Compra Venta Privada
  • Meta Description
    Formar parte del club de venta privada ofertix.com es totalmente gratuito y sin ningún compromiso. Ventas Exclusivas Primeras Marcas. Ofertix, The Shop Stock. Es un club de compra venta privada online que organiza, en exclusiva para sus socios, ventas puntuales de productos de primeras marcas con descuentos de hasta un 80%, en relación al precio de las tiendas. Zapatos, bolsos, ropa, complementos, relojes, deportes, bisutería, perfumería, electrónica de consumo. las mejores marcas a precios exclusivos en el club de venta privada Ofertix. No pierdas la oportunidad de ir a la última con las mejores marcas. Hazte socio de Ofertix, compra venta privada.

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    91.223.61.17
  • Domain Age
    6 Years, 1 Months, 25 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Wed, 04 Sep 2013 14:42:06 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-powered-by: PHP/5.3.17
  • cache-control: no-cache
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
nicline.com's WHOIS database is only for information purposes,
this information consists on domain name registration records.
nicline.com does not guarantee the accuracy of the information
contained in the WHOIS. nicline.com allows the use of the
information only for lawful purposes, under no circumstances this data
will be use for: (a) allow, enable, or otherwise support the transmission
by e-mail, telephone, or facsimile of mass unsolicited, commercial
advertising or solicitations to entities other than the data recipient's
own existing customers; or (b) enable high volume, automated,
electronic processes that send queries or data to the systems of
Registry Operator or any ICANN-Accredited Registrar, except as
reasonably necessary to register domain names or modify existing
registrations.


Distribuidor Autorizado:
Piensa Solutions
email
http://www.piensasolutions.com


Domain name: ofertix.com

Registrant:
antonio alcantara arroyo (SROW-1708102)

email
C Miguel Hernandez, 39
LHospitalet de Llobregat BARCELONA
08908 ES
+34 932012811


Administrative contact:
antonio alcantara arroyo (SRCO-2715803)
email
C Miguel Hernandez, 39
LHospitalet de Llobregat BARCELONA
08908 ES
+34 932012811


Technical contact:
Joan Valduvieco Llopart (SRCO-2715804)
email
C Miguel Hernandez, 39
LHospitalet de Llobregat BARCELONA
08908 ES
+34 932012811


Domain servers in listed order:
fs3.ofertix.com 213.195.72.192
fs9.ofertix.com 91.223.61.8
fs7.ofertix.com 31.222.163.31
fs8.ofertix.com 91.223.61.7


Created: 06 May 2007 20:30:04:710 UTC
Expires: 06 May 2014 18:30:09:000 UTC
Last updated: 02 Apr 2009 17:47:51:497 UTC

DNS Analysis


DNS servers
fs3.ofertix.com [213.195.72.192]
fs7.ofertix.com [31.222.163.31]
fs8.ofertix.com [91.223.61.7]
fs9.ofertix.com [91.223.61.8]


DNS Records

Answer records
ofertix.com TXT google-site-verification=hB7pcxuZ_8OIda4QMP48_eKBZQ-g2B-EdFi0FTvGh0E 300s
ofertix.com TXT v=spf1 a mx ip4:91.223.61.0/24 ip4:213.195.72.192 a:ALT1.ASPMX.L.GOOGLE.COM a:ALT2.ASPMX.L.GOOGLE.COM a:ASPMX2.GOOGLEMAIL.COM a:ASPMX3.GOOGLEMAIL.COM a:ASPMX4.GOOGLEMAIL.COM a:ASPMX5.GOOGLEMAIL.COM a:ASPMX.L.GOOGLE.COM ~all 300s
ofertix.com A 91.223.61.16 300s
ofertix.com A 91.223.61.17 300s
ofertix.com A 91.223.61.15 300s
ofertix.com SOA
server: fs3.ofertix.com
email: root@ofertix.com
serial: 2013011400
refresh: 28800
retry: 3600
expire: 1814400
minimum ttl: 3600
300s
ofertix.com NS  fs8.ofertix.com 300s
ofertix.com NS  fs9.ofertix.com 300s
ofertix.com NS  fs3.ofertix.com 300s
ofertix.com NS  fs7.ofertix.com 300s

Authority records

Additional records

IP 91.223.61.17 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 7 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.6007155635062612
Message Error
  • Error Line 13, Column 20: there is no attribute "property"
        <meta property="fb:admins" content="100002361841820" />

    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 39, Column 112: ID "switch" already defined
    …ia="screen" href="http://static02.ofertix.net/css/main_moda.css" id="switch" />

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 38, Column 117: ID "switch" first defined here
    …creen" href="http://static01.ofertix.net/css/main_moda_ocio.css" id="switch" />
  • Error Line 113, Column 63: there is no attribute "ajax"
    … action="/principal/updateLogin" ajax="1" update="entrada_login" method="post"…

    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 113, Column 74: there is no attribute "update"
    …action="/principal/updateLogin" ajax="1" update="entrada_login" method="post" >

    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 151, Column 85: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …nput id="categoria_actual" type="hidden" value="moda" name="categoria_actual"/>

    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 152, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
        <input id="promocion_login" type="hidden" value="" name="promocion_login"/>

    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 153, Column 89: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …d="promocion_lead_login" type="hidden" value="" name="promocion_lead_login"/>  

    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 154, Column 79: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    … <input id="acceso_login" type="hidden" value="login2" name="acceso_login"/>   

    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 157, Column 15: syntax of attribute value does not conform to declared value
          <ul id="">

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  • Error Line 159, Column 64: there is no attribute "placeholder"
    …text" name="login[email]" placeholder="Correo electrónico" id="login_email" />…

    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 272, Column 30: there is no attribute "alt"
                      <li><a alt=""><img class="carrusel_item" alt="banner" /></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 272, Column 74: required attribute "src" not specified
    …              <li><a alt=""><img class="carrusel_item" alt="banner" /></a></li>

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

  • Warning Line 303, Column 31: character "<" is the first character of a delimiter but occurred as data
    //          for (var n = 0; n < banners_slide.length - 1; n++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 312, Column 22: character "<" is the first character of a delimiter but occurred as data
                  if(idx < banners_relleno_slide){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 341, Column 83: character "&" is the first character of a delimiter but occurred as data
    …                                 <h2 class="escaparate_title">Nice & Crazy</h2>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 345, Column 97: there is no attribute "target"
    …    <a href="escaparate/link/see-by-chloe-10170" class="boxE1" target="_blank">

    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 346, Column 96: there is no attribute "name"
    …         <img alt="See by Chloé" name="See by Chloé10170" class="prod" src="ht…

    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 954, Column 87: cannot generate system identifier for general entity "hl"
    …tp://www.youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, hei…

    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 954, Column 87: general entity "hl" not defined and no default entity
    …tp://www.youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, hei…

    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 954, Column 89: reference not terminated by REFC delimiter
    …://www.youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, heigh…

    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 954, Column 89: reference to entity "hl" for which no system identifier could be generated
    …://www.youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, heigh…

    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 954, Column 86: entity was defined here
    …ttp://www.youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, he…
  • Warning Line 954, Column 96: cannot generate system identifier for general entity "fs"
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344})…

    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 954, Column 96: general entity "fs" not defined and no default entity
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344})…

    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 954, Column 98: reference not terminated by REFC delimiter
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});

    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 954, Column 98: reference to entity "fs" for which no system identifier could be generated
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});

    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 954, Column 95: entity was defined here
    ….youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344}…
  • Warning Line 954, Column 101: cannot generate system identifier for general entity "autoplay"
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});

    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 954, Column 101: general entity "autoplay" not defined and no default entity
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});

    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 954, Column 109: reference not terminated by REFC delimiter
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});

    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 954, Column 109: reference to entity "autoplay" for which no system identifier could be generated
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});

    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 954, Column 100: entity was defined here
    …youtube.com/v/'+youtube_id+'&hl=es_ES&fs=1&autoplay=1',width:425, height:344});
  • Error Line 962, Column 52: an attribute value must be a literal unless it contains only name characters
    … banners = [{"id":"6","html":"<a href=\"http:\/\/www.ofertix.com\/regalo\"><im…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 88: document type does not allow element "a" here
    …f=\"http:\/\/www.ofertix.com\/regalo\"><img src=\"http:\/\/www.ofertix.com\/im…

    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 962, Column 98: an attribute value must be a literal unless it contains only name characters
    …/\/www.ofertix.com\/regalo\"><img src=\"http:\/\/www.ofertix.com\/images\/bann…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 182: an attribute value must be a literal unless it contains only name characters
    …anner_tarjeta_regalo_moda.jpg\" style=\"display: block;\"\/><\/a>"},{"id":"14"…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 198: "block" is not a member of a group specified for any attribute
    …galo_moda.jpg\" style=\"display: block;\"\/><\/a>"},{"id":"14","html":"<a href…
  • Error Line 962, Column 203: required attribute "alt" not specified
    …moda.jpg\" style=\"display: block;\"\/><\/a>"},{"id":"14","html":"<a href=\"ht…

    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 962, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …oda.jpg\" style=\"display: block;\"\/><\/a>"},{"id":"14","html":"<a href=\"htt…

    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 962, Column 89: start tag was here
    …=\"http:\/\/www.ofertix.com\/regalo\"><img src=\"http:\/\/www.ofertix.com\/ima…
  • Warning Line 962, Column 204: character "<" is the first character of a delimiter but occurred as data
    …oda.jpg\" style=\"display: block;\"\/><\/a>"},{"id":"14","html":"<a href=\"htt…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 962, Column 239: an attribute value must be a literal unless it contains only name characters
    …\/><\/a>"},{"id":"14","html":"<a href=\"http:\/\/www.ofertix.com\/tienda\"><im…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 275: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …f=\"http:\/\/www.ofertix.com\/tienda\"><img style=\"display: block;\" src=\"ht…

    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 962, Column 287: an attribute value must be a literal unless it contains only name characters
    …/www.ofertix.com\/tienda\"><img style=\"display: block;\" src=\"http:\/\/www.o…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 303: "block" is not a member of a group specified for any attribute
    …\/tienda\"><img style=\"display: block;\" src=\"http:\/\/www.ofertix.com\/imag…
  • Error Line 962, Column 311: an attribute value must be a literal unless it contains only name characters
    …\"><img style=\"display: block;\" src=\"http:\/\/www.ofertix.com\/images\/bann…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 400: required attribute "alt" not specified
    …_fisica\/130201\/escaparate_moda.jpg\"><\/a>"},{"id":"78","html":"<a href=\"ht…

    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 962, Column 401: end tag for "img" omitted, but OMITTAG NO was specified
    …fisica\/130201\/escaparate_moda.jpg\"><\/a>"},{"id":"78","html":"<a href=\"htt…

    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 962, Column 276: start tag was here
    …=\"http:\/\/www.ofertix.com\/tienda\"><img style=\"display: block;\" src=\"htt…
  • Warning Line 962, Column 401: character "<" is the first character of a delimiter but occurred as data
    …fisica\/130201\/escaparate_moda.jpg\"><\/a>"},{"id":"78","html":"<a href=\"htt…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 962, Column 436: an attribute value must be a literal unless it contains only name characters
    …\"><\/a>"},{"id":"78","html":"<a href=\"http:\/\/www.ofertix.com\/belleza?idu=…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 483: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …\/www.ofertix.com\/belleza?idu=[IDU]\"><img style=\"display: block;\" src=\"ht…

    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 962, Column 495: an attribute value must be a literal unless it contains only name characters
    …x.com\/belleza?idu=[IDU]\"><img style=\"display: block;\" src=\"http:\/\/www.o…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 511: "block" is not a member of a group specified for any attribute
    …du=[IDU]\"><img style=\"display: block;\" src=\"http:\/\/www.ofertix.com\/imag…
  • Error Line 962, Column 519: an attribute value must be a literal unless it contains only name characters
    …\"><img style=\"display: block;\" src=\"http:\/\/www.ofertix.com\/images\/bann…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 606: there is no attribute "border"
    …ty\/130201\/beauty_MODA.jpg\"  border=\"0\" \/><\/a>"},{"id":"96","html":"<a h…

    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 962, Column 606: an attribute value must be a literal unless it contains only name characters
    …ty\/130201\/beauty_MODA.jpg\"  border=\"0\" \/><\/a>"},{"id":"96","html":"<a h…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 612: character "\" not allowed in attribute specification list
    …0201\/beauty_MODA.jpg\"  border=\"0\" \/><\/a>"},{"id":"96","html":"<a href=\"…
  • Error Line 962, Column 613: end tag for "img" omitted, but OMITTAG NO was specified
    …201\/beauty_MODA.jpg\"  border=\"0\" \/><\/a>"},{"id":"96","html":"<a href=\"h…

    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 962, Column 484: start tag was here
    …/www.ofertix.com\/belleza?idu=[IDU]\"><img style=\"display: block;\" src=\"htt…
  • Warning Line 962, Column 615: character "<" is the first character of a delimiter but occurred as data
    …1\/beauty_MODA.jpg\"  border=\"0\" \/><\/a>"},{"id":"96","html":"<a href=\"htt…

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 962, Column 650: an attribute value must be a literal unless it contains only name characters
    …\/><\/a>"},{"id":"96","html":"<a href=\"http:\/\/www.ofertix.com\/tienda\"><im…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 686: document type does not allow element "a" here; missing one of "object", "ins", "del", "span", "bdo", "tt", "i", "b", "big", "small", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label" start-tag
    …f=\"http:\/\/www.ofertix.com\/tienda\"><img style=\"display: block;\" src=\"ht…

    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 962, Column 698: an attribute value must be a literal unless it contains only name characters
    …/www.ofertix.com\/tienda\"><img style=\"display: block;\" src=\"http:\/\/www.o…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 714: "block" is not a member of a group specified for any attribute
    …\/tienda\"><img style=\"display: block;\" src=\"http:\/\/www.ofertix.com\/imag…
  • Error Line 962, Column 722: an attribute value must be a literal unless it contains only name characters
    …\"><img style=\"display: block;\" src=\"http:\/\/www.ofertix.com\/images\/bann…

    You have used a character that is not considered a "name character" in an attribute value. Which characters are considered "name characters" varies between the different document types, but a good rule of thumb is that unless the value contains only lower or upper case letters in the range a-z you must put quotation marks around the value. In fact, unless you have extreme file size requirements it is a very very good idea to always put quote marks around your attribute values. It is never wrong to do so, and very often it is absolutely necessary.

  • Error Line 962, Column 811: required attribute "alt" not specified
    …ix.com\/images\/banners\/tienda_fisica\/130201\/escaparate_moda.jpg\"><\/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 962, Column 812: end tag for "img" omitted, but OMITTAG NO was specified
    …ix.com\/images\/banners\/tienda_fisica\/130201\/escaparate_moda.jpg\"><\/a>"}];

    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 962, Column 687: start tag was here
    …=\"http:\/\/www.ofertix.com\/tienda\"><img style=\"display: block;\" src=\"htt…
  • Warning Line 962, Column 812: character "<" is the first character of a delimiter but occurred as data
    …ix.com\/images\/banners\/tienda_fisica\/130201\/escaparate_moda.jpg\"><\/a>"}];

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 965, Column 29: character "<" is the first character of a delimiter but occurred as data
              for (var n = 0; n < banners.length - 1; n++) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Warning Line 974, Column 20: character "<" is the first character of a delimiter but occurred as data
                if(idx < banners_relleno){

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 1003, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 962, Column 642: start tag was here
    …r=\"0\" \/><\/a>"},{"id":"96","html":"<a href=\"http:\/\/www.ofertix.com\/tien…
  • Error Line 1003, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 962, Column 428: start tag was here
    …moda.jpg\"><\/a>"},{"id":"78","html":"<a href=\"http:\/\/www.ofertix.com\/bell…
  • Error Line 1003, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 962, Column 231: start tag was here
    …block;\"\/><\/a>"},{"id":"14","html":"<a href=\"http:\/\/www.ofertix.com\/tien…
  • Error Line 1003, Column 9: end tag for "a" omitted, but OMITTAG NO was specified
    </script>

    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 962, Column 44: start tag was here
    …     var banners = [{"id":"6","html":"<a href=\"http:\/\/www.ofertix.com\/rega…
  • Warning Line 1047, Column 46: cannot generate system identifier for general entity "t"
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />

    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 1047, Column 46: general entity "t" not defined and no default entity
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />

    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 1047, Column 47: reference not terminated by REFC delimiter
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />

    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 1047, Column 47: reference to external entity in attribute value
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />

    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 1047, Column 47: reference to entity "t" for which no system identifier could be generated
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />

    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 1047, Column 45: entity was defined here
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />
  • Error Line 1047, Column 73: required attribute "alt" not specified
    <img src="http://ib.adnxs.com/seg?add=201037&t=2" width="1" height="1" />

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

  • Warning Line 1111, Column 52: character "<" is the first character of a delimiter but occurred as data
              if (document.cookie.indexOf(chkcookie,0) < 0) {

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.

Visitor Analysis

Daily Visitor
  • 6.300 visits