SmallWorlds is a new generation of virtual world that runs inside your web browser; combining media, web content, and casual games into a highly accessible & compelling 3D world. ...

smallworlds.com
  • Domain Name
    smallworlds.com
  • Favicon
  • Google Page Rank
    4
  • Alexa Rank
    #27584
  • Page Size
    10.8 KB
  • Ip Address
    54.243.77.141
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    3 GIF, 1 JPG, 0 PNG

Website Meta Analysis

  • Title
    SmallWorlds - Login
  • Meta Keyword
    virtual world, online world, avatar, mmo, mmop, mmorpg, free game, metaverse, 3d chat, 3d, chat, 3-d
  • Meta Description
    SmallWorlds is a new generation of virtual world that runs inside your web browser; combining media, web content, and casual games into a highly accessible & compelling 3D world.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    54.243.77.141
  • Domain Age
    9 Years, 0 Months, 20 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache, no-store
  • content-encoding: gzip
  • content-type: text/html; charset=UTF-8
  • date: Wed, 30 Jan 2013 04:59:15 GMT
  • p3p: CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT"
  • server: Apache
  • vary: Accept-Encoding,User-Agent
  • x-powered-by: PHP/5.3.2-1ubuntu4.11
  • content-length: 3553
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
Domain Domain Name: SMALLWORLDS.COM
Created: 27-Jan-04
Expires: 27-Jan-15
Updated: 11-Jan-10
Administrative Contact:
Private, Registration email
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax - (480) 624-2598
Technical Contact:
Private, Registration email
Domains by Proxy, Inc.
DomainsByProxy.com
15111 N. Hayden Rd., Ste 160, PMB 353
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax - (480) 624-2598
Name Servers:
NS19.DOMAINCONTROL.COM
NS20.DOMAINCONTROL.COM

DNS Analysis


DNS servers
ns-588.awsdns-09.net
ns-264.awsdns-33.com [205.251.193.8]
ns-1790.awsdns-31.co.uk
ns-1491.awsdns-58.org [205.251.197.211]


DNS Records

Answer records

Authority records

Additional records

IP 54.243.77.141 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Woodbridge
  • Continent Code
    07095
  • Latitude
    732
  • Longitude
    501
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 54.243.77.141"
    #
    # Use "?" to get help.
    #

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

    Amazon Technologies Inc. AMAZON-2011L (NET-54-240-0-0-1) 54.240.0.0 - 54.255.255.255
    Amazon.com, Inc. AMAZO-ZIAD1 (NET-54-242-0-0-1) 54.242.0.0 - 54.243.255.255


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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 14 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.45898244034218816
Message Error
  • Warning Line 8, Column 192: character "&" is the first character of a delimiter but occurred as data
    …b content, and casual games into a highly accessible & compelling 3D world." />

    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 71, Column 16: there is no attribute "onresize"
    <body onresize="resizeFooter()" onload="resizeFooter()">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  • Error Line 75, Column 8: required attribute "type" not specified
    <script>

    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 121, Column 42: end tag for element "br" which is not open
    			writeback("Transaction Completed! </br></br>"

    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 121, Column 47: end tag for element "br" which is not open
    			writeback("Transaction Completed! </br></br>"

    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 122, Column 41: end tag for element "br" which is not open
    				+ "Data returned from Facebook: </br>"

    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 123, Column 10: document type does not allow element "b" here
    				+ "<b>Order ID: </b>" + data['order_id'] + "</br>"

    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 123, Column 53: end tag for element "br" which is not open
    				+ "<b>Order ID: </b>" + data['order_id'] + "</br>"

    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 124, Column 10: document type does not allow element "b" here
    				+ "<b>Status: </b>" + data['status']);

    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 126, Column 39: end tag for element "br" which is not open
    			writeback("Transaction Failed! </br></br>"

    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 126, Column 44: end tag for element "br" which is not open
    			writeback("Transaction Failed! </br></br>"

    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 127, Column 49: end tag for element "br" which is not open
    				+ "Error message returned from Facebook:</br>"

    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 140, Column 240: required attribute "alt" not specified
    …der="0" style="border: none; position: absolute; top: 11px; left: 309px" /></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 141, Column 241: required attribute "alt" not specified
    …er="0" style="border: none; position: absolute; top: 163px; left: 241px" /></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 153, Column 98: required attribute "alt" not specified
    …://content.smallworlds.com/content-v3375/webassets/noscript_header.jpg" /></td>

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

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

  • Warning Line 210, Column 38: character "<" is the first character of a delimiter but occurred as data
    		else if (document.body.clientWidth < MIN_WIDTH)

    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.

Visitor Analysis

Daily Visitor
  • 6.300 visits
Daily Visitor