fuskator.com

fuskator.com has Alexa Rank 11.089 and Google Page Rank is 2

Display Widget for this domain on your website. Click Here
Processing update domain...

Overview Info

  • Domain Name
    fuskator.com
  • Favicon
  • Alexa Rank
    #11089
  • Google Page Rank
    PR 2
  • Ip Address
    95.211.228.147
  • Page Size
    81.3 KB
  • Images
    2 GIF, 52 JPG, 246 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    95.211.228.147
  • Domain Age
    3 Years, 7 Months, 12 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • server: nginx
  • date: Sat, 14 Sep 2013 20:54:35 GMT
  • content-type: text/html; charset=utf-8
  • content-length: 78365
  • connection: keep-alive
  • cache-control: private
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for fuskator.com

DNS Analysis


DNS servers
dns2.registrar-servers.com [208.64.122.242]
dns1.registrar-servers.com [38.101.213.194]
dns3.registrar-servers.com [173.224.125.12]
dns4.registrar-servers.com [173.236.55.99]
dns5.registrar-servers.com [188.138.2.23]


DNS Records

Answer records
fuskator.com NS  dns3.registrar-servers.com 1800s
fuskator.com NS  dns4.registrar-servers.com 1800s
fuskator.com NS  dns5.registrar-servers.com 1800s
fuskator.com NS  dns1.registrar-servers.com 1800s
fuskator.com TXT v=spf1 a mx ip4:5.39.68.193/32 -all 3600s
fuskator.com SOA
server: dns1.registrar-servers.com
email: hostmaster@registrar-servers.com
serial: 2013011400
refresh: 3600
retry: 1801
expire: 604800
minimum ttl: 3601
3601s
fuskator.com NS  dns2.registrar-servers.com 1800s
fuskator.com MX
preference: 10
exchange: mail.fuskator.com
1800s
fuskator.com A 95.211.132.112 3600s

Authority records

Additional records
mail.fuskator.com A 95.211.132.112 1800s

IP 95.211.228.147 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 10 Errors
  • 5 Warnings
Ratio Text/Html
  • 0.7464228648317455
Message Error
  • Warning Line 311, Column 60: cannot generate system identifier for general entity "ref"
    …<a href="http://www.juicyads.com/juicysites.php?id=11244&ref=9470">JuicyAds</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 311, Column 60: general entity "ref" not defined and no default entity
    …<a href="http://www.juicyads.com/juicysites.php?id=11244&ref=9470">JuicyAds</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 311, Column 63: reference not terminated by REFC delimiter
    …<a href="http://www.juicyads.com/juicysites.php?id=11244&ref=9470">JuicyAds</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 311, Column 63: reference to external entity in attribute value
    …<a href="http://www.juicyads.com/juicysites.php?id=11244&ref=9470">JuicyAds</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 311, Column 63: reference to entity "ref" for which no system identifier could be generated
    …<a href="http://www.juicyads.com/juicysites.php?id=11244&ref=9470">JuicyAds</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 311, Column 59: entity was defined here
    …<a href="http://www.juicyads.com/juicysites.php?id=11244&ref=9470">JuicyAds</a>
  • Warning Line 320, Column 35: character "&" is the first character of a delimiter but occurred as data
                    if (title != null && title != "") {

    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.
  • Warning Line 320, Column 36: character "&" is the first character of a delimiter but occurred as data
                    if (title != null && title != "") {

    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 357, Column 50: there is no attribute "data-size"
    …     <div class="g-plusone" data-size="medium" data-href="http://fuskator.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.

  • Error Line 357, Column 69: there is no attribute "data-href"
    …div class="g-plusone" data-size="medium" data-href="http://fuskator.com"></div>

    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 372, Column 39: there is no attribute "allowtransparency"
                        allowtransparency="true"></iframe>

    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 375, Column 91: there is no attribute "data-url"
    …/twitter.com/share" class="twitter-share-button" data-url="http://fuskator.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.

  • Error Line 376, Column 31: there is no attribute "data-text"
                        data-text="fuskator [NSFW]" data-via="fuskator" data-hashta…

    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 376, Column 58: there is no attribute "data-via"
    … data-text="fuskator [NSFW]" data-via="fuskator" data-hashtags="fuskator">Twee…

    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 376, Column 83: there is no attribute "data-hashtags"
    …a-text="fuskator [NSFW]" data-via="fuskator" data-hashtags="fuskator">Tweet</a>

    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 377, Column 24: required attribute "type" not specified
                    <script>!function (d, s, id) { var js, fjs = d.getElementsByTag…

    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>.

Visitor Analysis

Daily Visitor
  • 8.400 visits

In Page Analysis