Play the latest car games, supercar racing and tuning games. ...

hypercargames.com
  • Domain Name
    hypercargames.com
  • Favicon
  • Google Page Rank
    5
  • Alexa Rank
    #51368
  • Page Size
    24.8 KB
  • Ip Address
    74.86.4.29
  • Heading
    H1: 3, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    0 GIF, 26 JPG, 4 PNG

Website Meta Analysis

  • Title
    Car Games and Racing Games
  • Meta Keyword
    car games, supercar, racing, cars
  • Meta Description
    Play the latest car games, supercar racing and tuning games.

Technical Analysis

  • Webserver
    nginx admin
  • Ip Address
    74.86.4.29
  • Domain Age
    4 Years, 4 Months, 23 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx admin
  • date: Mon, 22 Jul 2013 16:12:15 GMT
  • content-type: text/html
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Fri, 19 Jul 2013 11:03:37 GMT
  • cache-control: max-age=0
  • expires: Mon, 22 Jul 2013 16:12:15 GMT
  • x-cache: HIT from Backend
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registration Service Provided By: ARPA media SRL
Contact: email
Visit: http://www.arpa.ro

Domain Name: hypercargames.com

Administrative Contact:
ARPA media SRL
Internet Solutions ( email )
+40.724242772
Fax:
str. Memorandumului nr. 8, ap.11
Cluj-Napoca, CLUJ 400659
RO

Technical Contact:
ARPA media SRL
Internet Solutions ( email )
+40.724242772
Fax:
str. Memorandumului nr. 8, ap.11
Cluj-Napoca, CLUJ 400659
RO

Registrant:
ARPA media SRL
Internet Solutions ()

Fax:
str. Memorandumului nr. 8, ap.11
Cluj-Napoca, CLUJ 400659
RO

Domain Status: Locked

Name Servers:
dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

Created: 22 Mar 2009 21:33:37
Expires: 22 Mar 2012 21:33:00

DNS Analysis


DNS servers
ns1dhl.name.com [184.172.60.181]
ns2kry.name.com [5.153.6.201]
ns3ghw.name.com [208.43.82.147]
ns4cfn.name.com [174.129.236.196]


DNS Records

Answer records
hypercargames.com A 174.120.158.131 300s
hypercargames.com MX
preference: 0
exchange: hypercargames.com
300s
hypercargames.com NS  ns4.name.com 300s
hypercargames.com SOA
server: ns1.name.com
email: support@name.com
serial: 1
refresh: 10800
retry: 3600
expire: 604800
minimum ttl: 3600
300s
hypercargames.com TXT v=spf1 a mx ?all 300s
hypercargames.com NS  ns2.name.com 300s
hypercargames.com NS  ns1.name.com 300s
hypercargames.com NS  ns3.name.com 300s

Authority records

Additional records
ns1.name.com A 184.173.68.159 86400s
ns4.name.com A 174.129.224.234 3600s
ns3.name.com A 184.173.144.32 86400s
ns2.name.com A 5.153.6.194 86400s
ns4.name.com A 174.129.236.114 3600s

IP 74.86.4.29 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 46 Errors
  • 4 Warnings
Ratio Text/Html
  • 0.680856086238099
Message Error
  • Error Line 15, Column 18: there is no attribute "HTTP-EQUIV"
    <META HTTP-EQUIV="Content-Language" Content="en"/>

    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 15, Column 45: there is no attribute "Content"
    <META HTTP-EQUIV="Content-Language" Content="en"/>

    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 15, Column 50: element "META" undefined
    <META HTTP-EQUIV="Content-Language" Content="en"/>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 20, Column 16: there is no attribute "property"
    <meta property="og:title" content="Play Racing Games on HyperCarGames.com"/>

    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.

  • Warning Line 84, Column 114: cannot generate system identifier for general entity "script"
    …/view.aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3…

    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 84, Column 114: general entity "script" not defined and no default entity
    …/view.aspx?poolid=" + cpmstar_pid + "&script=1&rnd=" + cpmstar_rnd + "'\x3e\x3…

    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.

Visitor Analysis

Daily Visitor
  • 3.500 visits