Homepage Favoritos Contactos Links Úteis Mapa do site Site PDA English Tempo Mar   Tempo presente Previsão significativa Previsão descritiva Previsão longo prazo Cartas meteorológicas Perfis verticais Imagens satélite Imagens radar Descargas ... ...

meteo.pt
  • Domain Name
    meteo.pt
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #244792
  • Page Size
    33.9 KB
  • Ip Address
    193.137.20.123
  • Heading
    H1: 1, H2: 1, H3: 8, H4: 0, H5: 0, H6: 0
  • Images
    15 GIF, 3 JPG, 24 PNG

Website Meta Analysis

  • Title
    Instituto Português do Mar e da Atmosfera
  • Meta Keyword
    Instituto Português do Mar e da Atmosfera, Mar, oceano, atmosfera, Instituto de Meteorologia, IPIMAR, o tempo, previsão do tempo, previsão meteorológica, clima, Portugal, sismologia, sismos
  • Meta Description
    Homepage Favoritos Contactos Links Úteis Mapa do site Site PDA English Tempo Mar   Tempo presente Previsão significativa Previsão descritiva Previsão longo prazo Cartas meteorológicas Perfis verticais Imagens satélite Imagens radar Descargas ...

Technical Analysis

  • Webserver
    Apache-Coyote/1.1
  • Ip Address
    193.137.20.123
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: Apache-Coyote/1.1
  • last-modified: Sun, 28 Apr 2013 07:48:10 GMT
  • content-type: text/html;charset=UTF-8
  • content-length: 31925
  • accept-ranges: bytes
  • date: Sun, 28 Apr 2013 07:57:40 GMT
  • age: 212
  • connection: keep-alive
  • via: 1.1 EurotuxBalancer
  • x-cache: HIT
  • x-cache-hits: 261
  • x-google-cache-control: remote-fetch
Nome de domínio / Domain Name: meteo.pt
Data de registo / Creation Date (dd/mm/yyyy): 29/09/1995
Data de expiração / Expiration Date (dd/mm/yyyy): 09/12/2012
Estado / Status: ACTIVE

Titular / Registrant
Instituto de Metereologia
Rua C ao Aeroporto de Lisboa
Lisboa
1749-077 Lisboa
Email: email ; email

Entidade Gestora / Billing Contact
Instituto de Metereologia
Email: email ; email

Responsável Técnico / Tech Contact
Jose Carlos de Oliveira Morais Monteiro
Email: email ; email

Nameserver Information
Nameserver: meteo.pt NS www-gw.meteo.pt.
Nameserver: meteo.pt NS ns02.fccn.pt.
Nameserver: www-gw.meteo.pt. A 193.137.20.1

DNS Analysis


DNS servers
ns02.fccn.pt [193.136.2.228]
www-gw.meteo.pt [193.137.20.1]


DNS Records

Answer records
meteo.pt SOA
server: www-gw.meteo.pt
email: postmaster@www-gw.meteo.pt
serial: 2012121801
refresh: 7200
retry: 3600
expire: 604800
minimum ttl: 14400
7200s
meteo.pt NS  perseus.ipma.pt 7200s
meteo.pt NS  www-gw.meteo.pt 7200s
meteo.pt NS  ns02.fccn.pt 7200s
meteo.pt A 193.137.20.123 7200s
meteo.pt MX
preference: 10
exchange: meteo.pt.mx42.mpsmx.net
7200s
meteo.pt MX
preference: 20
exchange: meteo.pt.mx43.mpsmx.net
7200s
meteo.pt MX
preference: 20
exchange: meteo.pt.mx44.mpsmx.net
7200s
meteo.pt MX
preference: 10
exchange: meteo.pt.mx41.mpsmx.net
7200s

Authority records

Additional records
www-gw.meteo.pt A 193.137.20.1 7200s
perseus.ipma.pt A 193.137.20.3 7200s

IP 193.137.20.123 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 193.137.20.123

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 55 Errors
  • 31 Warnings
Ratio Text/Html
  • 0.7049260657769578
Message Error
  • Error Line 73, Column 20: document type does not allow element "ul" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    	  <ul id="NavList">

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

  • Warning Line 296, Column 29: cannot generate system identifier for general entity "startInfo"
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…

    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 296, Column 29: general entity "startInfo" not defined and no default entity
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…

    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 296, Column 38: reference not terminated by REFC delimiter
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…

    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 296, Column 38: reference to entity "startInfo" for which no system identifier could be generated
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…

    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 296, Column 28: entity was defined here
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…
  • Warning Line 296, Column 48: cannot generate system identifier for general entity "basePath"
    …hVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resource…

    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 296, Column 48: general entity "basePath" not defined and no default entity
    …hVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resource…

    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 296, Column 56: reference not terminated by REFC delimiter
    …'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 296, Column 56: reference to entity "basePath" for which no system identifier could be generated
    …'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 296, Column 47: entity was defined here
    …shVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resourc…
  • Warning Line 296, Column 59: cannot generate system identifier for general entity "uv"
    …cale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/inter…

    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 296, Column 59: general entity "uv" not defined and no default entity
    …cale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/inter…

    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 296, Column 61: reference not terminated by REFC delimiter
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 296, Column 61: reference to entity "uv" for which no system identifier could be generated
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 296, Column 58: entity was defined here
    …ocale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/inte…
  • Warning Line 296, Column 64: cannot generate system identifier for general entity "altXML"
    …pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.u…

    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 296, Column 64: general entity "altXML" not defined and no default entity
    …pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.u…

    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 296, Column 70: reference not terminated by REFC delimiter
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 296, Column 70: reference to entity "altXML" for which no system identifier could be generated
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 296, Column 63: entity was defined here
    …=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.…
  • Warning Line 296, Column 73: cannot generate system identifier for general entity "xmlURL"
    …nfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh…

    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 296, Column 73: general entity "xmlURL" not defined and no default entity
    …nfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh…

    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 296, Column 79: reference not terminated by REFC delimiter
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 296, Column 79: reference to entity "xmlURL" for which no system identifier could be generated
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 296, Column 72: entity was defined here
    …Info=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_h…
  • Warning Line 319, Column 54: reference not terminated by REFC delimiter
    …"flashVars" value="locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlUR…

    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 319, Column 54: reference to external entity in attribute value
    …"flashVars" value="locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlUR…

    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 319, Column 54: reference to entity "startInfo" for which no system identifier could be generated
    …"flashVars" value="locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlUR…

    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 296, Column 28: entity was defined here
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…
  • Warning Line 319, Column 72: reference not terminated by REFC delimiter
    …"locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 319, Column 72: reference to external entity in attribute value
    …"locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 319, Column 72: reference to entity "basePath" for which no system identifier could be generated
    …"locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 296, Column 47: entity was defined here
    …shVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resourc…
  • Warning Line 319, Column 77: reference not terminated by REFC delimiter
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 319, Column 77: reference to external entity in attribute value
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 319, Column 77: reference to entity "uv" for which no system identifier could be generated
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 296, Column 58: entity was defined here
    …ocale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/inte…
  • Warning Line 319, Column 86: reference not terminated by REFC delimiter
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 319, Column 86: reference to external entity in attribute value
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 319, Column 86: reference to entity "altXML" for which no system identifier could be generated
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 296, Column 63: entity was defined here
    …=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.…
  • Warning Line 319, Column 95: reference not terminated by REFC delimiter
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 319, Column 95: reference to external entity in attribute value
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 319, Column 95: reference to entity "xmlURL" for which no system identifier could be generated
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 296, Column 72: entity was defined here
    …Info=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_h…
  • Error Line 323, Column 15: there is no attribute "src"
    			<embed src="/opencms/bin/flash/vrs1.1/prev.meteo.sam.portugal.swf" quality="…

    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 323, Column 79: there is no attribute "quality"
    …/prev.meteo.sam.portugal.swf" quality="high" background-color="#ffffff" vertic…

    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 323, Column 103: there is no attribute "background-color"
    ….swf" quality="high" background-color="#ffffff" vertical-align="middle" width=…

    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 323, Column 128: there is no attribute "vertical-align"
    …ground-color="#ffffff" vertical-align="middle" width="600" height="422" name="…

    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 323, Column 143: there is no attribute "width"
    …ffffff" vertical-align="middle" width="600" height="422" name="prev.meteo.sam.…

    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 323, Column 156: there is no attribute "height"
    …cal-align="middle" width="600" height="422" name="prev.meteo.sam.portugal" all…

    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 323, Column 167: there is no attribute "name"
    …middle" width="600" height="422" name="prev.meteo.sam.portugal" allowScriptAcc…

    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 323, Column 211: there is no attribute "allowScriptAccess"
    …meteo.sam.portugal" allowScriptAccess="sameDomain" allowFullScreen="false" fla…

    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 323, Column 240: there is no attribute "allowFullScreen"
    …ptAccess="sameDomain" allowFullScreen="false" flashVars="locale=pt&startInfo=f…

    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 323, Column 258: there is no attribute "flashVars"
    …in" allowFullScreen="false" flashVars="locale=pt&startInfo=forecast&basePath=/…

    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 323, Column 278: reference not terminated by REFC delimiter
    …"false" flashVars="locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlUR…

    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 323, Column 278: reference to external entity in attribute value
    …"false" flashVars="locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlUR…

    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 323, Column 278: reference to entity "startInfo" for which no system identifier could be generated
    …"false" flashVars="locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlUR…

    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 296, Column 28: entity was defined here
    				'flashVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=…
  • Warning Line 323, Column 296: reference not terminated by REFC delimiter
    …"locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 323, Column 296: reference to external entity in attribute value
    …"locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 323, Column 296: reference to entity "basePath" for which no system identifier could be generated
    …"locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/in…

    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 296, Column 47: entity was defined here
    …shVars', 'locale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resourc…
  • Warning Line 323, Column 301: reference not terminated by REFC delimiter
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 323, Column 301: reference to external entity in attribute value
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 323, Column 301: reference to entity "uv" for which no system identifier could be generated
    …le=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/interna…

    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 296, Column 58: entity was defined here
    …ocale=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/inte…
  • Warning Line 323, Column 310: reference not terminated by REFC delimiter
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 323, Column 310: reference to external entity in attribute value
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 323, Column 310: reference to entity "altXML" for which no system identifier could be generated
    …rtInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw…

    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 296, Column 63: entity was defined here
    …=pt&startInfo=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.…
  • Warning Line 323, Column 319: reference not terminated by REFC delimiter
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 323, Column 319: reference to external entity in attribute value
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 323, Column 319: reference to entity "xmlURL" for which no system identifier could be generated
    …recast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_hh_pt.xm…

    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 296, Column 72: entity was defined here
    …Info=forecast&basePath=/&uv=0&altXML=1&xmlURL=resources.www/internal.user/pw_h…
  • Error Line 323, Column 583: there is no attribute "type"
    …internal.user/ww_details_pt.xml" type="application/x-shockwave-flash" pluginsp…

    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 323, Column 627: there is no attribute "pluginspage"
    …cation/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashpl…

    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 323, Column 674: element "embed" undefined
    …x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer" />

    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 324, Column 12: element "noembed" undefined
    			<noembed>Mapa previsão meteorológica. <a href="/opencms/pt/html.jsp">Informa…

    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 362, Column 204: end tag for "img" omitted, but OMITTAG NO was specified
    …in/banners/banner_subs_183x90_pt.png" alt="Receba informação no seu email"></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 362, Column 67: start tag was here
    …encms/pt/produtoseservicos/index.jsp"><img class="marleft10 marright10" src="/…
  • Error Line 366, Column 194: end tag for "img" omitted, but OMITTAG NO was specified
    …rc="/export/sites/ipma/bin/banners/banner_apps_183x90.png" alt="apps ipma"></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 366, Column 81: start tag was here
    …toseservicos/index.jsp?page=apps.xml"><img class="marleft10 marright10" src="/…
  • Error Line 370, Column 198: end tag for "img" omitted, but OMITTAG NO was specified
    …pma/bin/banners/banner_tv_183x90_pt.png" alt="Previsão estado tempo na tv"></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 370, Column 66: start tag was here
    …pencms/pt/media/multimedia/index.jsp"><img class="marleft10 marright10" src="/…
  • Error Line 389, Column 88: there is no attribute "onSubmit"
    …orm" action="/pt/pesquisa/searchresult.jsp" onSubmit="return validateSearch()">

    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 390, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
        	<input type="hidden" name="index" value="ipma PT">

    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 390, Column 6: start tag was here
        	<input type="hidden" name="index" value="ipma PT">
  • Error Line 391, Column 54: end tag for "input" omitted, but OMITTAG NO was specified
        	<input type="hidden" name="field" value="title">

    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 391, Column 6: start tag was here
        	<input type="hidden" name="field" value="title">
  • Error Line 392, Column 57: end tag for "input" omitted, but OMITTAG NO was specified
        	<input type="hidden" name="field" value="keywords">

    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 392, Column 6: start tag was here
        	<input type="hidden" name="field" value="keywords">
  • Error Line 393, Column 56: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type="hidden" name="field" value="description">

    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 393, Column 2: start tag was here
    	<input type="hidden" name="field" value="description">
  • Error Line 394, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
    	<input type="hidden" name="field" value="content">

    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 394, Column 2: start tag was here
    	<input type="hidden" name="field" value="content">
  • Error Line 396, Column 95: there is no attribute "onFocus"
    …name="query" value="Pesquisa" onFocus="if(this.value=='Pesquisa') this.value='…

    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 397, Column 8: there is no attribute "onBlur"
    onBlur="if(this.value=='') this.value='Pesquisa'" >

    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 397, Column 52: end tag for "input" omitted, but OMITTAG NO was specified
    onBlur="if(this.value=='') this.value='Pesquisa'" >

    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 396, Column 6: start tag was here
        	<input type="text" class="pesq_int_box" id="query" name="query" value="Pes…
  • Error Line 398, Column 59: end tag for "input" omitted, but OMITTAG NO was specified
        	<input type="submit" class="pesq_button" value="ok" >

    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 398, Column 6: start tag was here
        	<input type="submit" class="pesq_button" value="ok" >

Visitor Analysis

Daily Visitor
  • 537 visits
Daily Visitor