Iniciar sessão criar conta Artigos Fertilidade e concepção Gravidez Desenvolvimento Fetal Parto e Pós-Parto Amamentação O meu bebé Os meus filhos Adoção Alimentação Bem estar e beleza Festinhas para o bebé Directório Lojas ...

demaeparamae.pt
  • Domain Name
    demaeparamae.pt
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #65030
  • Page Size
    70.8 KB
  • Ip Address
    77.91.204.80
  • Heading
    H1: 0, H2: 20, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    6 GIF, 28 JPG, 7 PNG

Website Meta Analysis

  • Title
    De Mãe para Mãe | gravidez, maternidade, bebés, filhos e amizade
  • Meta Keyword
  • Meta Description
    Iniciar sessão criar conta Artigos Fertilidade e concepção Gravidez Desenvolvimento Fetal Parto e Pós-Parto Amamentação O meu bebé Os meus filhos Adoção Alimentação Bem estar e beleza Festinhas para o bebé Directório Lojas Serviços Saúde Festas ...

Technical Analysis

  • Webserver
    Apache/2.2.8 (CentOS)
  • Ip Address
    77.91.204.80
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache/2.2.8 (CentOS)
  • x-powered-by: PHP/5.2.17
  • cache-control: public, max-age=21600
  • last-modified: Fri, 01 Mar 2013 16:29:47 +0000
  • expires: Sun, 11 Mar 1984 12:00:00 GMT
  • vary: Cookie,Accept-Encoding
  • etag: "1362155387"-gzip
  • content-encoding: gzip
  • content-type: text/html; charset=utf-8
  • content-length: 10552
  • date: Fri, 01 Mar 2013 17:58:01 GMT
  • x-varnish: 59164177 58108355
  • age: 5293
  • connection: keep-alive
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)
No data whois for demaeparamae.pt

DNS Analysis


DNS servers
ns2.softlayer.com [67.228.255.5]
ns1.softlayer.com [67.228.254.4]


DNS Records

Answer records
demaeparamae.pt SOA
server: ns1.softlayer.com
email: root@demaeparamae.pt
serial: 2012080600
refresh: 3600
retry: 300
expire: 604800
minimum ttl: 3600
86400s
demaeparamae.pt NS  ns2.softlayer.com 86400s
demaeparamae.pt NS  ns1.softlayer.com 86400s
demaeparamae.pt A 77.91.204.80 86400s
demaeparamae.pt MX
preference: 30
exchange: ASPMX4.GOOGLEMAIL.com
86400s
demaeparamae.pt MX
preference: 30
exchange: ASPMX5.GOOGLEMAIL.com
86400s
demaeparamae.pt MX
preference: 10
exchange: ASPMX.L.GOOGLE.com
86400s
demaeparamae.pt MX
preference: 20
exchange: ALT1.ASPMX.L.GOOGLE.com
86400s
demaeparamae.pt MX
preference: 20
exchange: ALT2.ASPMX.L.GOOGLE.com
86400s
demaeparamae.pt MX
preference: 30
exchange: ASPMX2.GOOGLEMAIL.com
86400s
demaeparamae.pt MX
preference: 30
exchange: ASPMX3.GOOGLEMAIL.com
86400s
demaeparamae.pt TXT google-site-verification=iBobNvhBa4hSJ8h_WqzXhyuVvJfMGe8SuVVhQDyEqq4 86400s
demaeparamae.pt TXT v=spf1 mx a:77.91.204.80 mx:amazonses.com include:amazonses.com ~all 86400s

Authority records

Additional records

IP 77.91.204.80 Analysis

  • Country Code
    PT
  • Country Code3
    PRT
  • Country Name
    Portugal
  • City
    EU
  • Continent Code
    39.5° North
  • Latitude
    8.
  • Longitude
  • No whois ip data for 77.91.204.80

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 34 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.5905979131010877
Message Error
  • Error Line 8, Column 16: there is no attribute "property"
    <meta property="fb:admins" content="1037704942" />

    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 75, Column 12: syntax of attribute value does not conform to declared value
    <body 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 88, Column 72: there is no attribute "onClick"
    …ent.write('<a href="http://demaeparamae.pt/loja/livros" onClick="_gaq.push([');

    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 89, Column 19: an attribute specification must start with a name or name token
    		document.write("'_trackEvent','Pub','Click','Livros Header'");

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 89, Column 19: document type does not allow element "a" here
    		document.write("'_trackEvent','Pub','Click','Livros Header'");

    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 91, Column 114: there is no attribute "border"
    …o/manual-para-pais_dia_mae.png' alt='Livros' border='0' id='livro-teaser' />");

    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 107, Column 79: there is no attribute "height"
    …eparamae.pt/ilovedemaeparamae" height="117px" width="132px" style="position: 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 107, Column 93: there is no attribute "width"
    …ovedemaeparamae" height="117px" width="132px" style="position: absolute; top: …

    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 108, Column 21: an attribute specification must start with a name or name token
        document.write("'_trackEvent','UX','BTM','I Love DMPM Topo'");

    An attribute name (and some attribute values) must start with one of a restricted set of characters. This error usually indicates that you have failed to add a closing quotation mark on a previous attribute value (so the attribute value looks like the start of a new attribute) or have used an attribute that is not defined (usually a typo in a common attribute name).

  • Error Line 108, Column 21: document type does not allow element "a" here
        document.write("'_trackEvent','UX','BTM','I Love DMPM Topo'");

    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 141, Column 99: end tag for "img" omitted, but OMITTAG NO was specified
    …/sites/demaeparamae.pt/themes/dmpm/images/icon-login.png" alt="Iniciar sessão">

    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 141, Column 10: start tag was here
    									<img src="/sites/demaeparamae.pt/themes/dmpm/images/icon-login.png" al…
  • Error Line 142, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …c="/sites/demaeparamae.pt/themes/dmpm/images/icon-conta.png" alt="criar conta">

    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 142, Column 46: start tag was here
    …ref="/utilizador">Iniciar sessão</a>  <img src="/sites/demaeparamae.pt/themes/…
  • Error Line 144, Column 91: end tag for "img" omitted, but OMITTAG NO was specified
    …="/sites/demaeparamae.pt/themes/dmpm/images/icon-pesquisa.png" alt="pesquisar">

    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 144, Column 4: start tag was here
    			<img src="/sites/demaeparamae.pt/themes/dmpm/images/icon-pesquisa.png" alt="…
  • Error Line 160, Column 101: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/sites/demaeparamae.pt/themes/dmpm/images/login-r.gif" alt="pesquisar"> 			

    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 160, Column 7: start tag was here
    			   <img id="login-r" src="/sites/demaeparamae.pt/themes/dmpm/images/login-r.…
  • Warning Line 202, Column 43: character "&" is the first character of a delimiter but occurred as data
        <li><a href="/forum/maes-bebes" >Mães & Bebés</a></li>  

    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 208, Column 39: character "&" is the first character of a delimiter but occurred as data
        <li><a href="/forum/geral" >Geral & Apresentação</a></li>   

    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 231, Column 131: end tag for "img" omitted, but OMITTAG NO was specified
    …aeparamae.pt/themes/dmpm/images/mulheres.gif" alt="Grávida, mãe e amiga"></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 231, Column 3: start tag was here
    		<img height="215px" width="245px"  src="/sites/demaeparamae.pt/themes/dmpm/im…
  • Error Line 564, Column 66: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …      <span class="field-content"><a href='artigos'><h2>Artigos</h2></a></span>

    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 635, Column 70: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …pan class="field-content"><a href='alimentacao'><h2>Alimentação</h2></a></span>

    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 706, Column 64: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …<span class="field-content"><a href='bebes'><h2>Nasceu um bebé!</h2></a></span>

    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 773, Column 136: required attribute "alt" not specified
    …mes"><img src='http://demaeparamae.pt/files/nomes-significados.jpg'></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>.

  • Error Line 773, Column 140: end tag for "img" omitted, but OMITTAG NO was specified
    …mes"><img src='http://demaeparamae.pt/files/nomes-significados.jpg'></a></span>

    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 773, Column 74: start tag was here
    …content"><a href="/ferramentas/nomes"><img src='http://demaeparamae.pt/files/n…
  • Error Line 777, Column 77: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …content"><a href="/ferramentas/nomes"><h2>Nomes mais escolhidos</h2></a></span>

    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 832, Column 164: required attribute "alt" not specified
    …'><img src='http://demaeparamae.pt/files/livro-manual-para-pais.jpg' /></a></p>

    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 850, Column 130: required attribute "alt" not specified
    …rio"><img src='http://demaeparamae.pt/files/consultorio_medico.jpg'></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>.

  • Error Line 850, Column 134: end tag for "img" omitted, but OMITTAG NO was specified
    …rio"><img src='http://demaeparamae.pt/files/consultorio_medico.jpg'></a></span>

    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 850, Column 68: start tag was here
    …field-content"><a href="/consultorio"><img src='http://demaeparamae.pt/files/c…
  • Error Line 854, Column 71: document type does not allow element "h2" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …an class="field-content"><a href="/consultorio"><h2>Consultório</h2></a></span>

    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 923, Column 231: required attribute "alt" not specified
    …mae.pt/sites/demaeparamae.pt/files/call-to-action-classificados.png' /></a></p>

    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 1097, Column 147: required attribute "alt" not specified
    … src='http://demaeparamae.pt/files/redes_sociais/dmpm_facebook.png' /></a></td>

    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 1098, Column 114: required attribute "alt" not specified
    …><img src='http://demaeparamae.pt/files/redes_sociais/dmpm_rss.png' /></a></td>

    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 1099, Column 119: required attribute "alt" not specified
    …g src='http://demaeparamae.pt/files/redes_sociais/dmpm_twitter.png' /></a></td>

    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 1215, Column 108: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …manager-17174941a127eca59276dd68178482b5" class="block block-google_admanager">

    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 1244, Column 98: end tag for element "SCRIPT" which is not open
    …/javascript" src="/sites/demaeparamae.pt/themes/dmpm/js/netscope2.js"></SCRIPT>

    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 1245, Column 16: there is no attribute "TYPE"
    <SCRIPT TYPE = "text/javascript">

    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 1245, Column 33: element "SCRIPT" undefined
    <SCRIPT TYPE = "text/javascript">

    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 1249, Column 9: end tag for "SCRIPT" 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 1245, Column 1: start tag was here
    <SCRIPT TYPE = "text/javascript">

Visitor Analysis

Daily Visitor
  • 2.333 visits
Daily Visitor