Ente autárquico encargado de administrar la política tributaria de la provincia de Buenos Aires. ...

arba.gov.ar
  • Domain Name
    arba.gov.ar
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #29308
  • Page Size
    9.5 KB
  • Ip Address
    170.155.16.10
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    2 GIF, 5 JPG, 0 PNG

Website Meta Analysis

  • Title
    Arba | Agencia de Recaudación de la Provincia de Buenos Aires
  • Meta Keyword
    ministerio de economia,ex rentas,buenos aires,impuesto,inmobiliario,inmuebles,automotor,embarcaciones,ingresos brutos,iibb,patentes,recaudacion,vencimiento,retenciones bancarias,sellos,tgb,transmision gratuita de bienes,agente,catastro
  • Meta Description
    Ente autárquico encargado de administrar la política tributaria de la provincia de Buenos Aires.

Technical Analysis

  • Webserver
    Microsoft-IIS/7.0
  • Ip Address
    170.155.16.10
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from arba.gov.ar.

HTML Analysis

  • cache-control: Private
  • pragma: no-cache
  • content-type: text/html
  • content-encoding: gzip
  • expires: Sat, 09 Mar 2013 09:01:46 GMT
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.0
  • x-powered-by: ASP.NET
  • date: Sat, 09 Mar 2013 09:01:46 GMT
  • content-length: 3202
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for arba.gov.ar

DNS Analysis


DNS servers
dns2.arba.gov.ar [170.155.17.130]
dns1.arba.gov.ar [170.155.17.129]

DNS Records

Answer records
arba.gov.ar A 170.155.16.10 1800s
arba.gov.ar SOA
server: dns1.arba.gov.ar
email: tping@arba.gov.ar
serial: 2012121001
refresh: 3600
retry: 900
expire: 86400
minimum ttl: 86400
1800s
arba.gov.ar NS  dns1.arba.gov.ar 1800s
arba.gov.ar NS  dns2.arba.gov.ar 1800s
arba.gov.ar MX
preference: 5
exchange: relay.arba.gov.ar
1800s
arba.gov.ar TXT v=spf1 ip4:170.155.16.100 mx ~all 1800s

Authority records

Additional records
dns1.arba.gov.ar A 170.155.17.129 1800s
dns2.arba.gov.ar A 170.155.17.130 1800s
relay.arba.gov.ar A 170.155.16.100 1800s

IP 170.155.16.10 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 8 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.7052426387606443
Message Error
  • Error Line 2, Column 1: no document type declaration; implying "<!DOCTYPE HTML SYSTEM>"
    <HTML>

    The checked page did not contain a document type ("DOCTYPE") declaration. The Validator has tried to validate with a fallback DTD, but this is quite likely to be incorrect and will generate a large number of incorrect error messages. It is highly recommended that you insert the proper DOCTYPE declaration in your document -- instructions for doing this are given above -- and it is necessary to have this declaration before the page can be declared to be valid.

  • Error Line 48, Column 18: there is no attribute "LEFTMARGIN"
    <body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" class="body…

    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 48, Column 32: there is no attribute "TOPMARGIN"
    <body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" class="body…

    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 48, Column 48: there is no attribute "MARGINWIDTH"
    …leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" class="bodyHOME" 

    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 48, Column 65: there is no attribute "MARGINHEIGHT"
    …leftmargin="0" topmargin="0" marginwidth="0" marginheight="0" class="bodyHOME" 

    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 55, Column 44: there is no attribute "BACKGROUND"
    …td width="10" rowspan="5"  background="Recursos/Imagenes/Inicio/sombraIZQ.png"…

    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 85, Column 79: document type does not allow element "LI" here; missing one of "UL", "OL", "DIR", "MENU" start-tag
    … 0px 0px 15px; vertical-align:middle" ><a href="Apartados/UsoInterno/UsoIntern…

    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 91, Column 215: NET-enabling start-tag requires SHORTTAG YES
    …er="0" id="InmAuEm" alt="Inmobiliario, Automotores y Embarcaciones" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 95, Column 177: NET-enabling start-tag requires SHORTTAG YES
    … width="185" height="45" border="0" id="IIBB" alt="Ingresos Brutos" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 99, Column 214: NET-enabling start-tag requires SHORTTAG YES
    …0" id="Sellos" alt="Sellos y Transmisi&oacute;n Gratuita de Bienes" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 103, Column 177: NET-enabling start-tag requires SHORTTAG YES
    …s.jpg" width="92" height="45" border="0" id="Agentes" alt="Agentes" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Warning Line 107, Column 181: NET-enabling start-tag requires SHORTTAG YES
    …jpg" width="91" height="45" border="0" id="Catastro" alt="Catastro" /></a></td>

    For the current document, the validator interprets strings like <FOO /> according to legacy rules that break the expectations of most authors and thus cause confusing warnings and error messages from the validator. This interpretation is triggered by HTML 4 documents or other SGML-based HTML documents. To avoid the messages, simply remove the "/" character in such contexts. NB: If you expect <FOO /> to be interpreted as an XML-compatible "self-closing" tag, then you need to use XHTML or HTML5.

    This warning and related errors may also be caused by an unquoted attribute value containing one or more "/". Example: <a href=http://w3c.org>W3C</a>. In such cases, the solution is to put quotation marks around the value.

  • Error Line 114, Column 137: there is no attribute "ONLOAD"
    …="735" height="400" frameborder="0"  id="visorPrensa" onload="ini();"></iframe>

    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.

Visitor Analysis

Daily Visitor
  • 5.133 visits
Daily Visitor