Foro de servicios eróticos y sexuales en Barcelona y alrededores. Masajes, relax, clubs, escorts, etc. ...

sexomercadobcn.com
  • Domain Name
    sexomercadobcn.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #43304
  • Page Size
    126.1 KB
  • Ip Address
    91.192.110.74
  • Heading
    H1: 1, H2: 1, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    183 GIF, 23 JPG, 2 PNG

Website Meta Analysis

  • Title
    SexoMercadoBCN
  • Meta Keyword
    Putas Escorts Masajes Relax Clubs Barcelona
  • Meta Description
    Foro de servicios eróticos y sexuales en Barcelona y alrededores. Masajes, relax, clubs, escorts, etc.

Technical Analysis

  • Webserver
    Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8g PHP/5.2.17
  • Ip Address
    91.192.110.74
  • Domain Age
    4 Years, 10 Months, 2 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Fri, 30 Aug 2013 00:02:38 GMT
  • server: Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/0.9.8g PHP/5.2.17
  • x-powered-by: PHP/5.2.17
  • cache-control: private
  • pragma: private
  • x-ua-compatible: IE=7
  • x-chromephp-data: eyJ2ZXJzaW9uIjoiMy4wIiwiY29sdW1ucyI6WyJsYWJlbCIsImxvZyIsImJhY2t0cmFjZSIsInR5cGUiXSwicm93cyI6W1tudWxsLFsidXNjX3NhbGlkYXBpc29zIiwiaGVhZGVyX2xvZ28iLCJhZnRlcl9mb3J1bXMiLCJoZWFkZXJfZW5kIiwicGFnZV9jb3JuZXIiLCJiZWxvd19uYXZiYXIiLCJiZWZvcmVmb290ZXIiLCJub3RpY2VfcmlnaHQiLCJhZnRlcmZvb3RlciIsImJlbG93X25hdmJpdCIsImJlZm9yZWZvb3Rlcl9mb3J1bWhvbWUiLCJmb3J1bWhvbWVfbWlkZGxlIiwiZm9ydW1ob21lcmlnaHQiLCJmb3J1bWhvbWVsZWZ0IiwiYWZ0ZXJfY29udGVudF9mb3J1bWhvbWUiLCJiZWZvcmVfY29udGVudF9mb3J1bWhvbWUiXSwiXC9mdXJhbmV0XC9zaXRlc1wvc2V4b21lcmNhZG9iY24uY29tXC93ZWJcL2h0ZG9jc1wvaW5jbHVkZXNcL3ZCU1wvTG9jYXRpb25Mb2cucGhwIDogNDgiLCIiXV0sInJlcXVlc3RfdXJpIjoiXC9mb3JvLnBocCJ9
  • content-type: text/html; charset=ISO-8859-1
  • 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.


Whois server: whois.nicline.com

Domain name: sexomercadobcn.com

Registrant:
PabloManuelCastroFernandez (SROW-1919806)

email
Aptdo de Correos n 58
Castelldefels Barcelona
08060 ES
+34 659444246


Administrative contact:
Social Visions BCN S.L. (SRCO-3057810)
email
Aptdo de Correos n 58
Castelldefels Barcelona
08860 ES
+34 659444246


Technical contact:
DHAP CENTER SL (SRCO-109757)
email
REY DON JAIME, 16
PATERNA VALENCIA
46980 ES
+34 902364151


Domain servers in listed order:
dns1.hispalisdns.com 195.78.228.199
dns2.hispalisdns.com 67.18.244.114


Created: 23 Oct 2008 00:01:24:287 UTC
Expires: 22 Oct 2013 00:00:00:000 UTC
Last updated: 22 Sep 2012 23:14:01:657 UTC



DNS Analysis


DNS servers
dns1.hispalisdns.com [195.78.228.199]
dns2.hispalisdns.com [67.18.244.114]
dns3.hispalisdns.com [213.186.47.218]


DNS Records

Answer records
sexomercadobcn.com SOA
server: dns1.hispalisdns.com
email: admin@furanet.com
serial: 2013010801
refresh: 3200
retry: 1600
expire: 604800
minimum ttl: 3600
3600s
sexomercadobcn.com A 91.192.110.74 3600s
sexomercadobcn.com MX
preference: 10
exchange: mail.sexomercadobcn.com
3600s
sexomercadobcn.com NS  dns1.hispalisdns.com 3600s
sexomercadobcn.com NS  dns2.hispalisdns.com 3600s
sexomercadobcn.com NS  dns3.hispalisdns.com 3600s
sexomercadobcn.com TXT v=spf1 a mx a:mail.sexomercadobcn.com ip4:195.78.228.0/22 ip4:91.192.108.0/22 ?all 3600s
sexomercadobcn.com 28 [16 bytes] 3600s

Authority records

Additional records
mail.sexomercadobcn.com A 91.192.110.74 3600s
dns1.hispalisdns.com A 195.78.228.199 3600s
dns2.hispalisdns.com A 67.18.244.114 3600s
dns3.hispalisdns.com A 213.186.47.218 3600s

IP 91.192.110.74 Analysis

  • Country Code
    ES
  • Country Code3
    ESP
  • Country Name
    Spain
  • City
    EU
  • Continent Code
    40° North
  • Latitude
    4.
  • Longitude
  • No whois ip data for 91.192.110.74

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 56 Errors
  • 6 Warnings
Ratio Text/Html
  • 0.726075137659441
Message Error
  • Error Line 11, Column 18: there is no attribute "http-equiv"
    <META http-equiv="Page-Enter" content="blendTrans(Duration=0.2)">

    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 11, Column 39: there is no attribute "content"
    <META http-equiv="Page-Enter" content="blendTrans(Duration=0.2)">

    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 11, Column 65: element "META" undefined
    <META http-equiv="Page-Enter" content="blendTrans(Duration=0.2)">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 12, Column 64: element "META" undefined
    <META http-equiv="Page-Exit" content="blendTrans(Duration=0.2)">

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 215, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 12, Column 1: start tag was here
    <META http-equiv="Page-Exit" content="blendTrans(Duration=0.2)">
  • Error Line 215, Column 7: end tag for "META" omitted, but OMITTAG NO was specified
    </head>

    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 11, Column 1: start tag was here
    <META http-equiv="Page-Enter" content="blendTrans(Duration=0.2)">
  • Error Line 215, Column 7: end tag for "head" which is not finished
    </head>

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

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

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

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

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

  • Error Line 366, Column 249: there is no attribute "data-href"
    …publi_code=468x60Sup_SXMDO" data-href="http://www.sexomercadobcn.com/vbvua_rd.…

    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 470, Column 20: document type does not allow element "tr" here
                    <tr>

    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 552, Column 61: required attribute "action" not specified
                <form name="livesearch" onsubmit="return false;">

    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 627, Column 115: required attribute "alt" not specified
    …cn.com/images/icons/foto24.gif" border="0" style="float:right; height:14px;" />

    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 632, Column 111: required attribute "alt" not specified
    …cadobcn.com/images/icons/expeFotosNueva.gif" border="0" style="height:14px;" />

    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 648, Column 170: required attribute "alt" not specified
    …bc44c65f_65976.jpg?dl=1359746581" border="0" style="width:100%;height:74px;" />

    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 656, Column 170: required attribute "alt" not specified
    …c1c2336d_65965.jpg?dl=1359745023" border="0" style="width:100%;height:74px;" />

    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 664, Column 170: required attribute "alt" not specified
    …e3e3ff2c_65895.jpg?dl=1359727266" border="0" style="width:100%;height:74px;" />

    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 672, Column 170: required attribute "alt" not specified
    …36f9f676_65785.jpg?dl=1359655681" border="0" style="width:100%;height:74px;" />

    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 680, Column 170: required attribute "alt" not specified
    …898c5476_65789.jpg?dl=1359656356" border="0" style="width:100%;height:74px;" />

    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 732, Column 94: document type does not allow element "table" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …span class="vbpua_ad" id="before_content_forumhome__159"><table align="center">

    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 771, Column 214: required attribute "alt" not specified
    …com/images/forum/normas.gif" align="left" vspace="4" hspace="4" border="0"></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 771, Column 218: end tag for "img" omitted, but OMITTAG NO was specified
    …com/images/forum/normas.gif" align="left" vspace="4" hspace="4" border="0"></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 771, Column 104: start tag was here
    …ormas-tutoriales-plantillas-f55.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 805, Column 201: required attribute "alt" not specified
    …cn.com/images/forum/bar.gif" align="left" vspace="4" hspace="4" border="0"></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 805, Column 205: end tag for "img" omitted, but OMITTAG NO was specified
    …cn.com/images/forum/bar.gif" align="left" vspace="4" hspace="4" border="0"></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 805, Column 94: start tag was here
    …obcn.com/bar-sexomercadobcn-f17.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 839, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    … Chicas, Locales, Agencias" align="left" vspace="4"  hspace="4" border="0"></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 839, Column 97: start tag was here
    …n.com/escorts-profesionales-f14.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 873, Column 258: end tag for "img" omitted, but OMITTAG NO was specified
    …fía para Escorts y Sexshops" align="left" vspace="4" hspace="4" border="0"></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 873, Column 95: start tag was here
    …bcn.com/fotografia-sexshops-f92.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 907, Column 273: end tag for "img" omitted, but OMITTAG NO was specified
    …r Horas, Hoteles de Parejas" align="left" vspace="4" hspace="4" border="0"></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 907, Column 98: start tag was here
    ….com/habitaciones-por-horas-f93.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 941, Column 256: end tag for "img" omitted, but OMITTAG NO was specified
    …ral, Intercambios de Pareja" align="left" vspace="4" hspace="4" border="0"></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 941, Column 97: start tag was here
    …n.com/mundo-swinger-liberal-f95.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 975, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …="Consultas sobre el Relax" align="left"  vspace="4" hspace="4" border="0"></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 975, Column 111: start tag was here
    …s-clasificaciones-concursos-f13.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1024, Column 241: end tag for "img" omitted, but OMITTAG NO was specified
    …"Pisos y Agencias de Relax" align="left"  vspace="4" hspace="4" border="0"></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 1024, Column 95: start tag was here
    …bcn.com/pisos-agencias-relax-f3.html"><img src="http://img.sexomercadobcn.com/…
  • Warning Line 1054, Column 106: character "<" is the first character of a delimiter but occurred as data
    …cas-tarifa-minima-100-f6.html"><strong>Chicas tarifa mínima < 100€</strong></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 1057, Column 179: character "<" is the first character of a delimiter but occurred as data
    …ages/forum/menos150.gif" alt="Escorts <150€" align="left"  vspace="4" hspace="…

    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 1057, Column 236: end tag for "img" omitted, but OMITTAG NO was specified
    …50.gif" alt="Escorts <150€" align="left"  vspace="4" hspace="4" border="0"></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 1057, Column 99: start tag was here
    …com/chicas-tarifa-minima-100-f6.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1091, Column 244: end tag for "img" omitted, but OMITTAG NO was specified
    …50.gif" alt="Escorts >100€" align="left"  vspace="4" hspace="4" border="0"></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 1091, Column 109: start tag was here
    …-agencias-tarifa-minima-100-f37.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1125, Column 204: required attribute "alt" not specified
    …/forum/asiaticas.gif" align="left"  vspace="4" hspace="4" border="0"></a></div>

    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 1125, Column 208: end tag for "img" omitted, but OMITTAG NO was specified
    …/forum/asiaticas.gif" align="left"  vspace="4" hspace="4" border="0"></a></div>

    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 1125, Column 90: start tag was here
    …rcadobcn.com/pisos-asiaticas-f8.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1157, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    …"Masajes, Tantra, Terapias" align="left"  vspace="4" hspace="4" border="0"></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 1157, Column 102: start tag was here
    …/masajistas-locales-masajes-f10.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1190, Column 203: required attribute "alt" not specified
    …mages/forum/pelus.gif" align="left" vspace="4" hspace="4" border="0"></a></div>

    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 1190, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …mages/forum/pelus.gif" align="left" vspace="4" hspace="4" border="0"></a></div>

    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 1190, Column 94: start tag was here
    …obcn.com/peluquerias-chinas-f54.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1222, Column 247: end tag for "img" omitted, but OMITTAG NO was specified
    …lubs, Puticlubs, Peepshows" align="left"  vspace="4" hspace="4" border="0"></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 1222, Column 99: start tag was here
    …com/clubs-alterne-peep-shows-f7.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1256, Column 208: required attribute "alt" not specified
    …com/images/forum/trans.gif" align="left"  vspace="4" hspace="4" border="0"></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 1256, Column 212: end tag for "img" omitted, but OMITTAG NO was specified
    …com/images/forum/trans.gif" align="left"  vspace="4" hspace="4" border="0"></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 1256, Column 98: start tag was here
    ….com/travestis-transexuales-f12.html"><img src="http://img.sexomercadobcn.com/…
  • Error Line 1424, Column 555: required attribute "alt" not specified
    …rcadobcn.com/banners/97/NuevoLoquo-468x60.jpg" title="NuevoLoquo" /></a></span>

    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 1559, Column 33: cannot generate system identifier for general entity "ajax"
    	$.get('misc.php?do=pollSummary&ajax=1', function(response){

    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 1559, Column 33: general entity "ajax" not defined and no default entity
    	$.get('misc.php?do=pollSummary&ajax=1', function(response){

    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 1559, Column 37: reference not terminated by REFC delimiter
    	$.get('misc.php?do=pollSummary&ajax=1', function(response){

    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 1559, Column 37: reference to entity "ajax" for which no system identifier could be generated
    	$.get('misc.php?do=pollSummary&ajax=1', function(response){

    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 1559, Column 32: entity was defined here
    	$.get('misc.php?do=pollSummary&ajax=1', function(response){
  • Warning Line 1563, Column 16: character "&" is the first character of a delimiter but occurred as data
    			if(response && $('error', response).length) {

    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 1563, Column 17: character "&" is the first character of a delimiter but occurred as data
    			if(response && $('error', response).length) {

    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 1645, Column 5: end tag for "div" omitted, but OMITTAG NO was specified
    </td>

    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 1643, Column 1: start tag was here
    <div class="smallfont" align="center">
  • Error Line 1661, Column 6: end tag for "td" omitted, but OMITTAG NO was specified
    </div>

    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 539, Column 1: start tag was here
    <td valign="top" width="100%">
  • Error Line 1661, Column 6: end tag for "tr" omitted, but OMITTAG NO was specified
    </div>

    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 537, Column 1: start tag was here
    <tr>
  • Error Line 1661, Column 6: end tag for "table" omitted, but OMITTAG NO was specified
    </div>

    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 536, Column 27: start tag was here
    <!-- / nav buttons bar --><table width="100%" cellpadding="0" cellspacing="0" b…
  • Error Line 1663, Column 5: end tag for element "td" which is not open
    </td>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1664, Column 28: document type does not allow element "td" here
    <td width="10" valign="top"><img src="http://img.sexomercadobcn.com/images/clea…

    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 1664, Column 110: required attribute "alt" not specified
    …g src="http://img.sexomercadobcn.com/images/clear.gif" border="0" width="10" />

    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 1667, Column 17: document type does not allow element "td" here
    <td valign="top">

    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 1699, Column 41: there is no attribute "border"
    	<th class="alt1" align="center" border="0" colspan="2">

    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 1867, Column 207: end tag for "img" omitted, but OMITTAG NO was specified
    …bcn.com/banner/concursos/bannerCamiseta.gif" border="0" alt="Camiseta SMB"></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 1867, Column 96: start tag was here
    …as-publicadas-t35986.html#post584171"><img src="http://ban1.sexomercadobcn.com…
  • Error Line 1873, Column 183: end tag for "img" omitted, but OMITTAG NO was specified
    …mercadobcn.com/banner/qrportada.jpg" border="0" alt="Cupones Descuento QR"></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 1873, Column 79: start tag was here
    …xpe-descuentos-codigo-qr-t61752.html"><img src="http://ban1.sexomercadobcn.com…
  • Error Line 1899, Column 193: end tag for "img" omitted, but OMITTAG NO was specified
    …/banner/ParticipaSMB.gif" border="0" alt="Promoción de Escorts y Agencias"></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 1899, Column 75: start tag was here
    …om/participacion-escorts-t38643.html"><img src="http://ban1.sexomercadobcn.com…
  • Error Line 1913, Column 5: end tag for "td" omitted, but OMITTAG NO was specified
    </tr>

    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 1674, Column 1: start tag was here
    <td>
  • Error Line 1914, Column 5: end tag for "tbody" omitted, but OMITTAG NO was specified
    </td>

    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 1672, Column 1: start tag was here
    <tbody id="collapseobj_usc_right" style="">
  • Error Line 1914, Column 5: end tag for "table" omitted, but OMITTAG NO was specified
    </td>

    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 1671, Column 1: start tag was here
    <table border="0" width="60" cellspacing="0" cellpadding="0">
  • Error Line 1915, Column 8: end tag for element "tbody" which is not open
    </tbody>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1916, Column 8: end tag for element "table" which is not open
    </table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1917, Column 5: end tag for element "td" which is not open
    </td>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1918, Column 17: document type does not allow element "td" here
    <td valign="top">

    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 1923, Column 5: end tag for element "tr" which is not open
    </tr>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1924, Column 8: end tag for element "table" which is not open
    </table>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 1928, Column 6: end tag for element "div" which is not open
    </div>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

Visitor Analysis

Daily Visitor
  • 1.808 visits