Bulk ammo for sale online at Target Sports USA. Free shipping available on all bulk ammunition for sale! ...

targetsportsusa.com
  • Domain Name
    targetsportsusa.com
  • Favicon
  • Google Page Rank
    2
  • Alexa Rank
    #51599
  • Page Size
    76 KB
  • Ip Address
    67.228.1.227
  • Heading
    H1: 0, H2: 0, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 76 JPG, 6 PNG

Website Meta Analysis

  • Title
    Target Sports USA | Discount Ammunition Online | Ammo For Sale | Free Shipping Ammunition
  • Meta Keyword
    bulk ammo, ammo for sale, ammunition for sale, bulk ammunition, free shipping
  • Meta Description
    Bulk ammo for sale online at Target Sports USA. Free shipping available on all bulk ammunition for sale!

Technical Analysis

  • Webserver
    Microsoft-IIS/7.5
  • Ip Address
    67.228.1.227
  • Domain Age
    3 Years, 6 Months, 22 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: private
  • pragma: no-cache
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • expires: Thu, 19 Sep 2013 14:13:32 GMT
  • vary: Accept-Encoding
  • server: Microsoft-IIS/7.5
  • x-aspnet-version: 2.0.50727
  • x-powered-by: ASP.NET
  • date: Thu, 19 Sep 2013 14:13:33 GMT
  • content-length: 20656
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for targetsportsusa.com

DNS Analysis


DNS servers
ns1.appliedi.net
ns2.appliedi.net


DNS Records

Answer records
targetsportsusa.com A 174.136.68.67 86400s
targetsportsusa.com NS  ns1.appliedi.net 86400s
targetsportsusa.com NS  ns2.appliedi.net 86400s
targetsportsusa.com SOA
server: ns1.appliedi.net
email: hostmaster@targetsportsusa.com
serial: 2011053112
refresh: 3600
retry: 600
expire: 1209600
minimum ttl: 86400
86400s
targetsportsusa.com MX
preference: 10
exchange: mail.targetsportsusa.com
86400s

Authority records

Additional records
mail.targetsportsusa.com A 174.136.73.214 86400s

IP 67.228.1.227 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 5 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.6455317345116829
Message Error
  • Error Line 1, Column 1: no document type declaration; will parse without validation
    <div style="position: fixed;bottom: 65px; color:#ffffff;background-color: #B909…

    The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.

    Learn how to add a doctype to your document from our FAQ, or use the validator's Document Type option to validate your document against a specific Document Type.

  • Warning Line 1, Column 456: NET-enabling start-tag requires SHORTTAG YES
    …DOTNETSTOREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="ht…

    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 1, Column 460: cannot generate system identifier for general entity "nbsp"
    …ETSTOREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http:/…

    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 1, Column 460: general entity "nbsp" not defined and no default entity
    …ETSTOREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http:/…

    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.

  • Error Line 1, Column 464: reference to entity "nbsp" for which no system identifier could be generated
    …OREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http://www…

    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 1, Column 459: entity was defined here
    …NETSTOREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http:…
  • Error Line 1, Column 470: reference to entity "nbsp" for which no system identifier could be generated
    …NT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http://www.aspdo…

    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 1, Column 459: entity was defined here
    …NETSTOREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http:…
  • Error Line 1, Column 476: reference to entity "nbsp" for which no system identifier could be generated
    …</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http://www.aspdotnetst…

    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 1, Column 459: entity was defined here
    …NETSTOREFRONT.COM</a> SOFTWARE!<br /> &nbsp;&nbsp;&nbsp;- Click <a href="http:…

Visitor Analysis

Daily Visitor
  • 4.667 visits