utiket.com

Cari harga tiket pesawat murah. Menemukan dan membandingkan harga tiket Lion air, Sriwijaya, Garuda, TransNusa, AirAsia, Merpati dan lain lain. ...

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    utiket.com
  • Favicon
  • Alexa Rank
    #20369
  • Google Page Rank
    PR 3
  • Ip Address
    216.185.115.34
  • Page Size
    76.8 KB
  • Images
    33 GIF, 20 JPG, 21 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 21 15 11 1 0

Website Meta Analysis



  • Title
    utiket.com: Tiket Pesawat Murah | Utiket.com | Cari Harga Tiket Pesawat Promo Murah
  • Meta Keyword
  • Meta Description
    Cari harga tiket pesawat murah. Menemukan dan membandingkan harga tiket Lion air, Sriwijaya, Garuda, TransNusa, AirAsia, Merpati dan lain lain.

Technical Analysis



  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    216.185.115.34
  • Domain Age
    2 Years, 7 Months, 1 days.
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • content-type: text/html
  • content-encoding: gzip
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-powered-by: ASP.NET
  • date: Tue, 17 Sep 2013 17:05:23 GMT
  • content-length: 17481
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
imade IT
Achter de Muur 2
Groningen, 9711PR
NL

Domain name: UTIKET.COM

Administrative Contact:
Logtenberg, E. email
Postbus 329
Groningen, 9700AH
NL
+31.505492234
Technical Contact:
Logtenberg, E. email
Postbus 329
Groningen, 9700AH
NL
+31.505492234


Record last updated on 01-Jan-2012.
Record expires on 30-Jan-2013.
Record created on 30-Jan-2011.


Domain servers in listed order:
NS2.VEVIDA.NET
NS3.VEVIDA.COM
NS1.VEVIDA.NET

Domain status: clientTransferProhibited
clientUpdateProhibited

DNS Analysis


DNS servers
ns3.vevida.com [77.94.248.30]
ns1.vevida.net
ns2.vevida.net


DNS Records

Answer records
utiket.com SOA
server: ns1.vevida.net
email: hostmaster@vevida.com
serial: 2013010102
refresh: 14400
retry: 1800
expire: 1209600
minimum ttl: 900
900s
utiket.com A 216.185.115.34 900s
utiket.com MX
preference: 20
exchange: backup-mx.vevida.com
900s
utiket.com MX
preference: 10
exchange: mx1.vevida.com
900s
utiket.com MX
preference: 10
exchange: mx2.vevida.com
900s
utiket.com MX
preference: 10
exchange: mx3.vevida.com
900s
utiket.com MX
preference: 10
exchange: mx4.vevida.com
900s
utiket.com NS  ns3.vevida.com 900s
utiket.com NS  ns1.vevida.net 900s
utiket.com NS  ns2.vevida.net 900s

Authority records

Additional records
mx1.vevida.com A 77.94.249.37 900s
mx1.vevida.com 28 [16 bytes] 900s
mx2.vevida.com A 77.94.249.56 900s
mx2.vevida.com 28 [16 bytes] 900s
mx3.vevida.com A 77.94.249.40 900s
mx3.vevida.com 28 [16 bytes] 900s
mx4.vevida.com A 77.94.249.34 900s
mx4.vevida.com 28 [16 bytes] 900s
backup-mx.vevida.com A 80.84.240.248 900s
backup-mx.vevida.com A 77.94.249.33 900s
ns1.vevida.net A 77.94.248.29 900s

IP 216.185.115.34 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Houston
  • Continent Code
    77002
  • Latitude
    713
  • Longitude
    618
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.185.115.34"
    #
    # Use "?" to get help.
    #

    #
    # The following results may also be obtained via:
    # http://whois.arin.net/rest/nets;q=216.185.115.34?showDetails=true&showARIN=false&ext=netref2
    #

    Global Datacenter SNG-216-185-115-0-24 (NET-216-185-115-0-1) 216.185.115.0 - 216.185.115.255
    ThePlanet.com Internet Services, Inc. NETBLK-THEPLANET-BLK-3 (NET-216-185-96-0-1) 216.185.96.0 - 216.185.127.255


    #
    # ARIN WHOIS data and services are subject to the Terms of Use
    # available at: https://www.arin.net/whois_tou.html
    #

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 4 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.7323143049709424
Message Error
  • Error Line 11, Column 16: there is no attribute "property"
    <meta property="og:image" content="http://www.utiket.com/images/logo/utiket.gif…

    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 24: document type does not allow element "strong" here
    var txtinvalid='<strong>Pilihan tanggal tidak valid!</strong><p>Tanggalmu kemba…

    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 55, Column 64: document type does not allow element "p" here
    …ilihan tanggal tidak valid!</strong><p>Tanggalmu kembali adalah sebelum tangga…

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

  • Warning Line 242, Column 96: character "&" is the first character of a delimiter but occurred as data
    …utiket.com/indonesia/weblog/"  target="_top" class="mainbutton">News & Blog</a>

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 278, Column 192: required attribute "alt" not specified
    …ght="14" width="14" style="float:right;;margin-left:2px;margin-top:1px;" /></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 312, Column 113: required attribute "alt" not specified
    …"http://www.utiket.com/images/search-here.png" height="30" class="floatleft" />

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 1040, Column 93: cannot generate system identifier for general entity "m"
    …tp://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nb…

    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 1040, Column 93: general entity "m" not defined and no default entity
    …tp://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nb…

    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 1040, Column 94: reference not terminated by REFC delimiter
    …p://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbs…

    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 1040, Column 94: reference to external entity in attribute value
    …p://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbs…

    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 1040, Column 94: reference to entity "m" for which no system identifier could be generated
    …p://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbs…

    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 1040, Column 92: entity was defined here
    …ttp://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&n…
  • Warning Line 1040, Column 97: cannot generate system identifier for general entity "t"
    …/opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&…

    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 1040, Column 97: general entity "t" not defined and no default entity
    …/opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&…

    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 1040, Column 98: reference not terminated by REFC delimiter
    …opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&n…

    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 1040, Column 98: reference to external entity in attribute value
    …opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&n…

    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 1040, Column 98: reference to entity "t" for which no system identifier could be generated
    …opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&n…

    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 1040, Column 96: entity was defined here
    …//opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;…
  • Error Line 1040, Column 125: required attribute "alt" not specified
    ….yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&nbsp;

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 1041, Column 94: reference not terminated by REFC delimiter
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1041, Column 94: reference to external entity in attribute value
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1041, Column 94: reference to entity "m" for which no system identifier could be generated
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1040, Column 92: entity was defined here
    …ttp://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&n…
  • Warning Line 1041, Column 98: reference not terminated by REFC delimiter
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1041, Column 98: reference to external entity in attribute value
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1041, Column 98: reference to entity "t" for which no system identifier could be generated
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1040, Column 96: entity was defined here
    …//opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;…
  • Error Line 1041, Column 125: required attribute "alt" not specified
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1050, Column 40: there is no attribute "data-href"
    …			<div class="fb-like-box" data-href="http://www.facebook.com/Utiket" data-wi…

    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 1050, Column 84: there is no attribute "data-width"
    …//www.facebook.com/Utiket" data-width="300" data-height="400" data-show-faces=…

    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 1050, Column 102: there is no attribute "data-height"
    …/Utiket" data-width="300" data-height="400" data-show-faces="true" data-stream…

    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 1050, Column 124: there is no attribute "data-show-faces"
    …00" data-height="400" data-show-faces="true" data-stream="false" data-header="…

    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 1050, Column 143: there is no attribute "data-stream"
    …ght="400" data-show-faces="true" data-stream="false" data-header="false"></div>

    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 1050, Column 163: there is no attribute "data-header"
    …ght="400" data-show-faces="true" data-stream="false" data-header="false"></div>

    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 1138, Column 51: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    …le="font-size:9px;padding-top:6px;"><p>Memilih penginapan atau hotel saat libu…

    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 1139, Column 11: end tag for "p" omitted, but OMITTAG NO was specified
    					</div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1138, Column 7: start tag was here
    						<p style="font-size:9px;padding-top:6px;"><p>Memilih penginapan atau hote…
  • Error Line 1315, Column 8: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		  	<p><a href="http://www.utiket.com/id/tiket-pesawat/ke-singapore-sin.html">…

    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 1316, Column 128: required attribute "alt" not specified
    …es/plus.png" height="9" class="onclick" onclick="openfooter('citiesopen')"></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 1316, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …es/plus.png" height="9" class="onclick" onclick="openfooter('citiesopen')"></p>

    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 1316, Column 18: start tag was here
    		  	&nbsp;&nbsp;<img src="http://www.utiket.com/images/plus.png" height="9" cl…
  • Error Line 1317, Column 48: document type does not allow element "div" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    		  	<div style="display:none;" id="citiesopen">

    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 1326, Column 9: end tag for "p" omitted, but OMITTAG NO was specified
    			</div>		  	

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1325, Column 6: start tag was here
    		  	<p><a href="http://www.utiket.com/id/tiket-pesawat/ke-manila-mnl.html">Man…
  • Error Line 1327, Column 8: end tag for "p" omitted, but OMITTAG NO was specified
    		</div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1314, Column 6: start tag was here
    		  	<p><a href="http://www.utiket.com/id/tiket-pesawat/ke-balikpapan-bpn.html"…
  • Error Line 1338, Column 128: required attribute "alt" not specified
    …es/plus.png" height="9" class="onclick" onclick="openfooter('routesopen')"></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 1338, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …es/plus.png" height="9" class="onclick" onclick="openfooter('routesopen')"></p>

    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 1338, Column 18: start tag was here
    		  	&nbsp;&nbsp;<img src="http://www.utiket.com/images/plus.png" height="9" cl…
  • Error Line 1360, Column 128: required attribute "alt" not specified
    …/plus.png" height="9" class="onclick" onclick="openfooter('airlinesopen')"></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 1360, Column 132: end tag for "img" omitted, but OMITTAG NO was specified
    …/plus.png" height="9" class="onclick" onclick="openfooter('airlinesopen')"></p>

    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 1360, Column 16: start tag was here
    			&nbsp;&nbsp;<img src="http://www.utiket.com/images/plus.png" height="9" clas…
  • Error Line 1366, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_jetstar_airways-j…

    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 1367, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_kalstar_aviation-…

    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 1369, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_maswings-mh.html"…

    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 1370, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_nok_air-dd.html">…

    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 1371, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_orient_thai_airli…

    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 1372, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_seair-dg.html">SE…

    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 1373, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_sky_aviation-sy.h…

    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 1374, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_susi_air-si.html"…

    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 1375, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_tiger_airways-tr.…

    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 1376, Column 6: document type does not allow element "p" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_vietjet_airlines-…

    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 1377, Column 9: end tag for "p" omitted, but OMITTAG NO was specified
    			</div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1365, Column 4: start tag was here
    			<p><a href="http://www.utiket.com/id/airlines/tiketpesawat_firefly-fy.html">…
  • Error Line 1402, Column 207: end tag for element "span" which is not open
    …p://www.utiket.com/id/contact.html" rel="nofollow" >Contact form</a></span></p>

    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.

  • Warning Line 1404, Column 90: reference not terminated by REFC delimiter
    …p://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbs…

    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 1404, Column 90: reference to external entity in attribute value
    …p://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbs…

    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 1404, Column 90: reference to entity "m" for which no system identifier could be generated
    …p://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbs…

    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 1040, Column 92: entity was defined here
    …ttp://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&n…
  • Warning Line 1404, Column 94: reference not terminated by REFC delimiter
    …opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&n…

    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 1404, Column 94: reference to external entity in attribute value
    …opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&n…

    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 1404, Column 94: reference to entity "t" for which no system identifier could be generated
    …opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&n…

    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 1040, Column 96: entity was defined here
    …//opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;…
  • Error Line 1404, Column 121: required attribute "alt" not specified
    ….yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;&nbsp;

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Warning Line 1405, Column 91: reference not terminated by REFC delimiter
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1405, Column 91: reference to external entity in attribute value
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1405, Column 91: reference to entity "m" for which no system identifier could be generated
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1040, Column 92: entity was defined here
    …ttp://opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&n…
  • Warning Line 1405, Column 95: reference not terminated by REFC delimiter
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1405, Column 95: reference to external entity in attribute value
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1405, Column 95: reference to entity "t" for which no system identifier could be generated
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    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 1040, Column 96: entity was defined here
    …//opi.yahoo.com/online?u=utiketcom&m=g&t=1" border="0" height="18"/></a>&nbsp;…
  • Error Line 1405, Column 122: required attribute "alt" not specified
    …"http://opi.yahoo.com/online?u=utiketcom1&m=g&t=1" border="0" height="18"/></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1413, Column 144: required attribute "alt" not specified
    …//img3.utiket.com/images/facebook-icon.png" border="0" height="30" /></a>&nbsp;

    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 1414, Column 142: required attribute "alt" not specified
    …="http://img3.utiket.com/images/twitter-icon.png" border="0" height="30" /></a>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  • Error Line 1419, Column 8: end tag for "p" omitted, but OMITTAG NO was specified
    		</div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1417, Column 3: start tag was here
    		<p class="copyright" style="text-align:center;"><br/><strong>&#169; 2011 - 20…
  • Error Line 1420, Column 122: required attribute "alt" not specified
    …ogo/utiket black.jpg" height="50" class="floatright" style="margin-top:10px;"/>

    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 1424, Column 6: end tag for element "div" which is not open
    </div></div>

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

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

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

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

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

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

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

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

Visitor Analysis

Daily Visitor
  • 8.633 visits

In Page Analysis