SGAmmo.com is your #1 source for pistol, rifle, shotgun and rimfire ammunition. Everything is in stock and we have the best prices and selection around. ...

sgammo.com
  • Domain Name
    sgammo.com
  • Favicon
  • Google Page Rank
    3
  • Alexa Rank
    #48279
  • Page Size
    51.5 KB
  • Ip Address
    216.185.151.147
  • Heading
    H1: 1, H2: 8, H3: 0, H4: 0, H5: 0, H6: 0
  • Images
    1 GIF, 19 JPG, 3 PNG

Website Meta Analysis

  • Title
    SGAmmo.com | Family Owned and Operated, Stillwater Oklahoma
  • Meta Keyword
    ammo, discount ammo, bulk ammo, cheap ammo, buy ammo, ammo for sale, ammo sales online, surplus ammo, sgammo, sg ammo, ammunition, pistol ammo, rifle ammo, shotgun ammo, rimfire ammo
  • Meta Description
    SGAmmo.com is your #1 source for pistol, rifle, shotgun and rimfire ammunition. Everything is in stock and we have the best prices and selection around.

Technical Analysis

  • Webserver
    Apache
  • Ip Address
    216.185.151.147
  • Domain Age
    3 Years, 7 Months, 3 days.
  • Javascript Library
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • date: Thu, 18 Jul 2013 09:53:52 GMT
  • server: Apache
  • x-powered-by: PHP/5.4.11
  • last-modified: Thu, 18 Jul 2013 09:53:16 GMT
  • etag: "70860f895462c31edb12407ee1a25f90"
  • expires: Sun, 19 Nov 1978 05:00:00 GMT
  • cache-control: must-revalidate
  • vary: Accept-Encoding,User-Agent
  • content-encoding: gzip
  • content-length: 8815
  • connection: close
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Performance ammunition center
8423 S Perkins Rd
stillwater, Oklahoma 74074
United States

Domain Name: SGAMMO.COM
Created: 03-Dec-09
Expires: 03-Dec-14
Updated: 22-Jun-10

Administrative Contact:
gabbert, samuel email
Performance ammunition center
8423 S Perkins Rd
stillwater, Oklahoma 74074
United States
(405) 614-1418 Fax - (405) 385-0301

Technical Contact:
gabbert, samuel email
Performance ammunition center
8423 S Perkins Rd
stillwater, Oklahoma 74074
United States
(405) 614-1418 Fax - (405) 385-0301

Name Servers:
NS.INBOXINC.COM
NS2.INBOXINC.COM

DNS Analysis


DNS servers
ns.inboxinc.com [64.94.136.11]
ns2.inboxinc.com [64.237.45.34]


DNS Records

Answer records
sgammo.com A 216.185.151.147 3600s
sgammo.com NS  ns4.inboxinc.com 3600s
sgammo.com NS  ns5.inboxinc.com 3600s
sgammo.com NS  ns2.inboxinc.com 3600s
sgammo.com NS  ns.inboxinc.com 3600s
sgammo.com NS  ns3.inboxinc.com 3600s
sgammo.com SOA
server: ns.inboxinc.com
email: info@inboxinc.com
serial: 2012092118
refresh: 21600
retry: 7200
expire: 604800
minimum ttl: 3600
3600s
sgammo.com MX
preference: 10
exchange: mail.sgammo.com
3600s
sgammo.com TXT v=spf1 mx a:www.sgammo.com ?all 3600s

Authority records

Additional records
ns4.inboxinc.com A 69.41.170.223 3600s
ns5.inboxinc.com A 212.100.247.15 3600s
ns2.inboxinc.com A 64.237.45.34 3600s
ns.inboxinc.com A 64.94.136.11 3600s
ns3.inboxinc.com A 64.94.136.13 3600s
mail.sgammo.com A 174.143.68.200 3600s

IP 216.185.151.147 Analysis

  • Country Code
    US
  • Country Code3
    USA
  • Country Name
    United States
  • City
    Austin
  • Continent Code
    78702
  • Latitude
    512
  • Longitude
    635
  • #
    # Query terms are ambiguous. The query is assumed to be:
    # "n 216.185.151.147"
    #
    # Use "?" to get help.
    #

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

    Hostway Services, Inc. AFFINITY-AUSTIN-3 (NET-216-185-144-0-1) 216.185.144.0 - 216.185.159.255
    Affinity Internet, Inc AFFINET-BLK-1 (NET-216-185-128-0-1) 216.185.128.0 - 216.185.159.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
  • 5 Errors
  • 12 Warnings
Ratio Text/Html
  • 0.6671718702637163
Message Error
  • Error Line 2, Column 74: there is no attribute "class"
    …s="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en" class="standard-page">

    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 195, Column 175: there is no attribute "target"
    …llerAuctions.aspx?User=807924" target="_blank"><img src="/sites/default/files/…

    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 512, Column 56: there is no attribute "oncontextmenu"
    …rn open_tg_cert(this);" oncontextmenu="return tg_context();"><img onload="tg_i…

    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 512, Column 91: there is no attribute "onload"
    …nu="return tg_context();"><img onload="tg_image_load(this);" name="security-59…

    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 512, Column 119: there is no attribute "name"
    …mg onload="tg_image_load(this);" name="security-5935-small-white.gif" alt="Sec…

    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 513, Column 72: cannot generate system identifier for general entity "seal"
    …uard.com/seals/trust-seal.php?id=5935&seal=security&size=small&color=white&pag…

    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 513, Column 72: general entity "seal" not defined and no default entity
    …uard.com/seals/trust-seal.php?id=5935&seal=security&size=small&color=white&pag…

    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 513, Column 76: reference not terminated by REFC delimiter
    ….com/seals/trust-seal.php?id=5935&seal=security&size=small&color=white&pagetyp…

    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 513, Column 76: reference to external entity in attribute value
    ….com/seals/trust-seal.php?id=5935&seal=security&size=small&color=white&pagetyp…

    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 513, Column 76: reference to entity "seal" for which no system identifier could be generated
    ….com/seals/trust-seal.php?id=5935&seal=security&size=small&color=white&pagetyp…

    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 513, Column 71: entity was defined here
    …guard.com/seals/trust-seal.php?id=5935&seal=security&size=small&color=white&pa…
  • Warning Line 513, Column 86: cannot generate system identifier for general entity "size"
    …/trust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" />…

    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 513, Column 86: general entity "size" not defined and no default entity
    …/trust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" />…

    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 513, Column 90: reference not terminated by REFC delimiter
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 90: reference to external entity in attribute value
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 90: reference to entity "size" for which no system identifier could be generated
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 85: entity was defined here
    …s/trust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /…
  • Warning Line 513, Column 97: cannot generate system identifier for general entity "color"
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 97: general entity "color" not defined and no default entity
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 102: reference not terminated by REFC delimiter
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 102: reference to external entity in attribute value
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 102: reference to entity "color" for which no system identifier could be generated
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 96: entity was defined here
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></a>
  • Warning Line 513, Column 109: cannot generate system identifier for general entity "pagetype"
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 109: general entity "pagetype" not defined and no default entity
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 117: reference not terminated by REFC delimiter
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 117: reference to external entity in attribute value
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 117: reference to entity "pagetype" for which no system identifier could be generated
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></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 513, Column 108: entity was defined here
    …ust-seal.php?id=5935&seal=security&size=small&color=white&pagetype=demo" /></a>
  • Error Line 515, Column 5: end tag for "br" omitted, but OMITTAG NO was specified
    <br>

    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 515, Column 1: start tag was here
    <br>

Visitor Analysis

Daily Visitor
  • 1.983 visits