gtasanandreas.net

gtasanandreas.net

The GTA Network presents the most comprehensive fansite for the new Grand Theft Auto game: GTA San Andreas. Release dates and information for the PC, PlayStation 2 and Xbox titles. ...

Domain Name gtasanandreas.net
Favicon gtasanandreas.net
Google Page Rank 4
Alexa Rank #72058
Page Size 40.5 KB
Ip Address 192.95.29.180
Heading H1: 0, H2: 0, H3: 1, H4: 0, H5: 0, H6: 0
Images 32 GIF, 6 JPG, 10 PNG

Website Meta Analysis

Title GTA San Andreas : Overview
Meta Keyword gta, san andreas, gta: san andreas, grand theft auto: san andreas, grand theft auto, gta sanan, gtasanan, san andreas ps2, san andreas xbox, san andreas pc, cheats, walkthrough, guide, help, news
Meta Description The GTA Network presents the most comprehensive fansite for the new Grand Theft Auto game: GTA San Andreas. Release dates and information for the PC, PlayStation 2 and Xbox titles.

Technical Analysis

Webserver nginx/1.1.19
Ip Address 192.95.29.180
Domain Age
Javascript Library
Language used HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx/1.1.19
  • date: Sat, 02 Mar 2013 07:41:26 GMT
  • content-type: text/html
  • connection: keep-alive
  • content-encoding: gzip
  • content-length: 10361
  • age: 237
  • x-google-cache-control: remote-cache-hit
  • via: HTTP/1.1 GWA (remote cache hit)

No data whois for gtasanandreas.net

IP 192.95.29.180 Analysis

Country Code :
Country Code3 :
Country Name :
City :
Continent Code :
Latitude :
Longitude :

#
# Query terms are ambiguous. The query is assumed to be:
# "n 192.95.29.180"
#
# Use "?" to get help.
#

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

NetRange: 192.95.0.0 - 192.95.63.255
CIDR: 192.95.0.0/18
OriginAS: AS16276
NetName: OVH-ARIN-5
NetHandle: NET-192-95-0-0-1
Parent: NET-192-0-0-0-0
NetType: Direct Allocation
RegDate: 2012-12-07
Updated: 2012-12-07
Ref: http://whois.arin.net/rest/net/NET-192-95-0-0-1

OrgName: OVH Hosting, Inc.
OrgId: HO-2
Address: 625, avenue du President Kennedy
Address: Bureau 310
City: Montreal
StateProv: QC
PostalCode: H3A 1K2
Country: CA
RegDate: 2011-06-22
Updated: 2012-04-17
Ref: http://whois.arin.net/rest/org/HO-2

OrgAbuseHandle: NOC11876-ARIN
OrgAbuseName: NOC
OrgAbusePhone: +33 9 74 53 13 23
OrgAbuseEmail: noc@ovh.net
OrgAbuseRef: http://whois.arin.net/rest/poc/NOC11876-ARIN

OrgTechHandle: NOC11876-ARIN
OrgTechName: NOC
OrgTechPhone: +33 9 74 53 13 23
OrgTechEmail: noc@ovh.net
OrgTechRef: http://whois.arin.net/rest/poc/NOC11876-ARIN

#
# 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
  • 2 Errors
  • 10 Warnings
Ratio Text/Html

0.4867203316301938

Message Error
  • Warning Line 211, Column 146: NET-enabling start-tag requires SHORTTAG YES
    …/single.php?id=3958"> MTA: San Andreas Deathmatch - Developer Preview</a><br />

    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 212, Column 59: NET-enabling start-tag requires SHORTTAG YES
    <a href="/news/single.php?id=3933"> The Chain Game</a><br />

    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 213, Column 63: NET-enabling start-tag requires SHORTTAG YES
    <a href="/news/single.php?id=3930"> GTA: Treasure Hunt</a><br />

    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 214, Column 74: NET-enabling start-tag requires SHORTTAG YES
    <a href="/news/single.php?id=3924"> SA-MP Update: v0.2.2 Released</a><br />

    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 215, Column 83: NET-enabling start-tag requires SHORTTAG YES
    …ef="/news/single.php?id=3884"> San Andreas Multiplayer v0.2 Released!</a><br />

    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 219, Column 166: NET-enabling start-tag requires SHORTTAG YES
    …s/single.php?id=4500">Grand Theft Auto V is Coming September 17, 2013</a><br />

    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 220, Column 106: NET-enabling start-tag requires SHORTTAG YES
    …om/news/single.php?id=4499">New GTAV Artwork shows up in retail store</a><br />

    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 221, Column 98: NET-enabling start-tag requires SHORTTAG YES
    …gtanet.com/news/single.php?id=4498">New Grand Theft Auto V Screenshot</a><br />

    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 222, Column 110: NET-enabling start-tag requires SHORTTAG YES
    …ews/single.php?id=4496">GTAV Fan Trailer with Niko, Luis &amp; Johnny</a><br />

    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 223, Column 109: NET-enabling start-tag requires SHORTTAG YES
    …news/single.php?id=4494">Interviews with Rockstar North's Aaron & Les</a><br />

    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 406, Column 140: delimiter "'" invalid: only S separators and TAGC allowed here
    …9337a.cgi/v=2.0S/sz=120x600A|160x600A/'+rnum+'/RETURN-CODE/JS/"></scr'+'ipt>');
  • Error Line 406, Column 140: end tag for element "SCR" which is not open
    …9337a.cgi/v=2.0S/sz=120x600A|160x600A/'+rnum+'/RETURN-CODE/JS/"></scr'+'ipt>');

    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

3.383 visits

Daily Visitor