semprot.org

Forum Semprot Buka Bukaan 17 ini adalah tempat tempat ngobrol asyik untuk kamu semua. ...

This data was last updated from 16-11-2014 11:14:46  (update).

Overview Info



  • Domain Name
    semprot.org
  • Favicon
  • Alexa Rank
    #0
  • Google Page Rank
    1
  • Ip Address
    104.28.24.27
  • Page Size
    132 KB
  • Images
    55 GIF, 0 JPG, 126 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    1 33 2 101 8 0

Website Meta Analysis



  • Title
    Forum Semprot Buka Bukaan 17 Tahun (BB17)
  • Meta Keyword
    forum semprot,bb17,buka bukaan 17,adult,mesum
  • Meta Description
    Forum Semprot Buka Bukaan 17 ini adalah tempat tempat ngobrol asyik untuk kamu semua.

Technical Analysis



  • Webserver
    LiteSpeed
  • Ip Address
    104.28.24.27
  • Domain Age
  • Javascript Library
    jquery, yui
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from semprot.org.

HTML Analysis

  • date: Sun, 16 Nov 2014 11:14:41 GMT
  • server: LiteSpeed
  • connection: close
  • x-powered-by: PHP/5.3.28
  • cache-control: public, max-age=1
  • expires: Sun, 16 Nov 2014 11:14:42 GMT
  • content-type: text/html
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for semprot.org

DNS Analysis


DNS servers
dan.ns.cloudflare.com [173.245.59.108]
elsa.ns.cloudflare.com [173.245.58.111]


DNS Records

Answer records
semprot.org A 141.101.116.59 300s
semprot.org A 141.101.117.59 300s
semprot.org NS  dan.ns.cloudflare.com 86400s
semprot.org NS  elsa.ns.cloudflare.com 86400s
semprot.org SOA
server: dan.ns.cloudflare.com
email: [email protected]
serial: 2013071211
refresh: 10000
retry: 2400
expire: 604800
minimum ttl: 3600
86400s

Authority records

Additional records

IP 104.28.24.27 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 18 Errors
  • 3 Warnings
Ratio Text/Html
  • 0.7256134538301113
Message Error
  • Error Line 96, Column 10: document type does not allow element "noscript" here; assuming missing "object" start-tag
    <noscript><img src="https://d5nxst8fruw4z.cloudfront.net/atrk.gif?account=K1xLf…
  • Error Line 146, Column 8: document type does not allow element "title" here
    	<title>Forum Semprot Buka Bukaan 17 Tahun (BB17)</title>

    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 149, Column 122: document type does not allow element "link" here
    …f="clientscript/vbulletin_css/style00001l/forumhome-rollup.css?d=1416126833" />

    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 154, Column 120: document type does not allow element "link" here
    …/css" href="clientscript/vbulletin_css/style00001l/sidebar.css?d=1416126833" />

    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 155, Column 113: document type does not allow element "link" here
    …/css" href="clientscript/vbulletin_css/style00001l/widgets.css?d=1416126833" />

    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 156, Column 114: document type does not allow element "link" here
    …css" href="clientscript/vbulletin_css/style00001l/tagcloud.css?d=1416126833" />

    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 168, Column 116: document type does not allow element "link" here
    …s" href="clientscript/vbulletin_css/style00001l/additional.css?d=1416126833" />

    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 170, Column 7: end tag for "object" omitted, but OMITTAG NO was specified
    </head>

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

  • Info Line 96, Column 1: start tag was here
    <noscript><img src="https://d5nxst8fruw4z.cloudfront.net/atrk.gif?account=K1xLf…
  • Error Line 170, Column 7: end tag for "head" which is not finished
    </head>

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

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

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

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

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

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

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

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

  • Error Line 364, Column 30: document type does not allow element "ul" here; assuming missing "li" start-tag
    			<ul class="floatcontainer">
  • Error Line 382, Column 25: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li  id="tab_odiw_226">

    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 389, Column 25: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li  id="tab_nde5_205">

    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 396, Column 25: document type does not allow element "li" here; missing one of "ul", "ol", "menu", "dir" start-tag
    		<li  id="tab_odk0_789">

    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 397, Column 45: cannot generate system identifier for general entity "template"
    …a class="navtab" href="misc.php?do=page&template=livescore">Live Score Bola</a>

    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 397, Column 45: general entity "template" not defined and no default entity
    …a class="navtab" href="misc.php?do=page&template=livescore">Live Score Bola</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.

  • Warning Line 397, Column 53: reference not terminated by REFC delimiter
    …a class="navtab" href="misc.php?do=page&template=livescore">Live Score Bola</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 397, Column 53: reference to external entity in attribute value
    …a class="navtab" href="misc.php?do=page&template=livescore">Live Score Bola</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 397, Column 53: reference to entity "template" for which no system identifier could be generated
    …a class="navtab" href="misc.php?do=page&template=livescore">Live Score Bola</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 397, Column 44: entity was defined here
    …a class="navtab" href="misc.php?do=page&template=livescore">Live Score Bola</a>
  • Error Line 404, Column 6: end tag for "li" omitted, but OMITTAG NO was specified
    	</ul>

    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 364, Column 4: start tag was here
    			<ul class="floatcontainer">

Visitor Analysis

Daily Visitor
  • 29 visits

In Page Analysis