megafilmeshd.net

megafilmeshd.net has Alexa Rank 3.250 and Google Page Rank is 3

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

Overview Info

  • Domain Name
    megafilmeshd.net
  • Favicon
  • Alexa Rank
    #3250
  • Google Page Rank
    PR 3
  • Ip Address
    108.162.206.245
  • Page Size
    10.3 KB
  • Images
    0 GIF, 0 JPG, 0 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 0 0 0 0 0

Website Meta Analysis



  • Meta Keyword

Technical Analysis



  • Webserver
    cloudflare-nginx
  • Ip Address
    108.162.206.245
  • Domain Age
    3 Years, 1 Months, 27 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from megafilmeshd.net.

HTML Analysis

  • server: cloudflare-nginx
  • date: Fri, 13 Sep 2013 18:15:04 GMT
  • content-type: text/html; charset=UTF-8
  • connection: keep-alive
  • vary: Accept-Encoding
  • last-modified: Fri, 13 Sep 2013 18:00:02 GMT
  • cache-control: max-age=3, must-revalidate
  • expires: Fri, 13 Sep 2013 18:15:07 GMT
  • cf-ray: ad6d21cf2f305bb
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Domain Name: MEGAFILMESHD.NET
Created on: 03-Aug-10
Expires on: 03-Aug-13
Last Updated on: 08-Jul-12

Registrant:
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States

Administrative Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Technical Contact:
Private, Registration email
Domains By Proxy, LLC
DomainsByProxy.com
14747 N Northsight Blvd Suite 111, PMB 309
Scottsdale, Arizona 85260
United States
(480) 624-2599 Fax -- (480) 624-2598

Domain servers in listed order:
NS1.CDMON.NET
NS2.CDMON.NET
NS3.CDMON.NET

DNS Analysis


DNS servers
ns1.cdmon.net [212.36.74.129]
ns2.cdmon.net [46.16.60.60]
ns3.cdmon.net [95.211.8.207]


DNS Records

Answer records
megafilmeshd.net SOA
server: ns1.cdmon.net
email: hostmaster@megafilmeshd.net
serial: 1348150185
refresh: 10000
retry: 3600
expire: 604800
minimum ttl: 21600
2560s
megafilmeshd.net NS  ns1.cdmon.net 21600s
megafilmeshd.net NS  ns2.cdmon.net 21600s
megafilmeshd.net NS  ns3.cdmon.net 21600s
megafilmeshd.net A 95.211.117.18 900s

Authority records

Additional records
ns1.cdmon.net A 212.36.74.129 86400s
ns2.cdmon.net A 46.16.60.60 86400s
ns3.cdmon.net A 95.211.8.207 86400s

IP 108.162.206.245 Analysis

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

Site Same Ip

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 13 Errors
  • 1 Warnings
Ratio Text/Html
  • 0.8082696120079298
Message Error
  • Error Line 65, Column 54: required attribute "type" not specified
    <script src="http://megafilmeshd.net/js/modernizr.js"></script>

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

  • Error Line 65, Column 54: document type does not allow element "script" here; assuming missing "body" start-tag
    <script src="http://megafilmeshd.net/js/modernizr.js"></script>
  • Error Line 66, Column 62: required attribute "type" not specified
    <script src="http://megafilmeshd.net/js/modernizr-1.5.min.js"></script>

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

  • Error Line 68, Column 6: document type does not allow element "body" here
    <body>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  • Error Line 77, Column 118: there is no attribute "width"
    …invisivel.png" title="Buscar !" width="89" height="35" class="enviar" type="im…

    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 77, Column 130: there is no attribute "height"
    …ivel.png" title="Buscar !" width="89" height="35" class="enviar" type="image"/>

    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 159, Column 121: cannot generate system identifier for general entity "layout"
    …/pages/Mega-Filmes-HD/222689077746634&layout=standard&%0Ashow_faces=false&widt…

    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 159, Column 121: general entity "layout" not defined and no default entity
    …/pages/Mega-Filmes-HD/222689077746634&layout=standard&%0Ashow_faces=false&widt…

    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 159, Column 127: reference not terminated by REFC delimiter
    …/Mega-Filmes-HD/222689077746634&layout=standard&%0Ashow_faces=false&width=380&…

    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 159, Column 127: reference to external entity in attribute value
    …/Mega-Filmes-HD/222689077746634&layout=standard&%0Ashow_faces=false&width=380&…

    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 159, Column 127: reference to entity "layout" for which no system identifier could be generated
    …/Mega-Filmes-HD/222689077746634&layout=standard&%0Ashow_faces=false&width=380&…

    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 159, Column 120: entity was defined here
    …m/pages/Mega-Filmes-HD/222689077746634&layout=standard&%0Ashow_faces=false&wid…
  • Warning Line 159, Column 136: character "&" is the first character of a delimiter but occurred as data
    …mes-HD/222689077746634&layout=standard&%0Ashow_faces=false&width=380&action=li…

    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 159, Column 157: cannot generate system identifier for general entity "width"
    …4&layout=standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&…

    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 159, Column 157: general entity "width" not defined and no default entity
    …4&layout=standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&…

    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 159, Column 162: reference not terminated by REFC delimiter
    …out=standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&heigh…

    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 159, Column 162: reference to external entity in attribute value
    …out=standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&heigh…

    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 159, Column 162: reference to entity "width" for which no system identifier could be generated
    …out=standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&heigh…

    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 159, Column 156: entity was defined here
    …34&layout=standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light…
  • Warning Line 159, Column 167: cannot generate system identifier for general entity "action"
    …tandard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&height=25&…

    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 159, Column 167: general entity "action" not defined and no default entity
    …tandard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&height=25&…

    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 159, Column 173: reference not terminated by REFC delimiter
    …d&%0Ashow_faces=false&width=380&action=like&colorscheme=light&height=25&locale…

    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 159, Column 173: reference to external entity in attribute value
    …d&%0Ashow_faces=false&width=380&action=like&colorscheme=light&height=25&locale…

    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 159, Column 173: reference to entity "action" for which no system identifier could be generated
    …d&%0Ashow_faces=false&width=380&action=like&colorscheme=light&height=25&locale…

    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 159, Column 166: entity was defined here
    …standard&%0Ashow_faces=false&width=380&action=like&colorscheme=light&height=25…
  • Warning Line 159, Column 179: cannot generate system identifier for general entity "colorscheme"
    …how_faces=false&width=380&action=like&colorscheme=light&height=25&locale=pt_BR…

    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 159, Column 179: general entity "colorscheme" not defined and no default entity
    …how_faces=false&width=380&action=like&colorscheme=light&height=25&locale=pt_BR…

    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 159, Column 190: reference not terminated by REFC delimiter
    …alse&width=380&action=like&colorscheme=light&height=25&locale=pt_BR" style="bo…

    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 159, Column 190: reference to external entity in attribute value
    …alse&width=380&action=like&colorscheme=light&height=25&locale=pt_BR" style="bo…

    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 159, Column 190: reference to entity "colorscheme" for which no system identifier could be generated
    …alse&width=380&action=like&colorscheme=light&height=25&locale=pt_BR" style="bo…

    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 159, Column 178: entity was defined here
    …show_faces=false&width=380&action=like&colorscheme=light&height=25&locale=pt_B…
  • Warning Line 159, Column 197: cannot generate system identifier for general entity "height"
    …dth=380&action=like&colorscheme=light&height=25&locale=pt_BR" style="border:no…

    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 159, Column 197: general entity "height" not defined and no default entity
    …dth=380&action=like&colorscheme=light&height=25&locale=pt_BR" style="border:no…

    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 159, Column 203: reference not terminated by REFC delimiter
    …0&action=like&colorscheme=light&height=25&locale=pt_BR" style="border:none; ov…

    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 159, Column 203: reference to external entity in attribute value
    …0&action=like&colorscheme=light&height=25&locale=pt_BR" style="border:none; ov…

    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 159, Column 203: reference to entity "height" for which no system identifier could be generated
    …0&action=like&colorscheme=light&height=25&locale=pt_BR" style="border:none; ov…

    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 159, Column 196: entity was defined here
    …idth=380&action=like&colorscheme=light&height=25&locale=pt_BR" style="border:n…
  • Warning Line 159, Column 207: cannot generate system identifier for general entity "locale"
    …tion=like&colorscheme=light&height=25&locale=pt_BR" style="border:none; overfl…

    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 159, Column 207: general entity "locale" not defined and no default entity
    …tion=like&colorscheme=light&height=25&locale=pt_BR" style="border:none; overfl…

    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 159, Column 213: reference not terminated by REFC delimiter
    …ike&colorscheme=light&height=25&locale=pt_BR" style="border:none; overflow:hid…

    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 159, Column 213: reference to external entity in attribute value
    …ike&colorscheme=light&height=25&locale=pt_BR" style="border:none; overflow:hid…

    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 159, Column 213: reference to entity "locale" for which no system identifier could be generated
    …ike&colorscheme=light&height=25&locale=pt_BR" style="border:none; overflow:hid…

    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 159, Column 206: entity was defined here
    …ction=like&colorscheme=light&height=25&locale=pt_BR" style="border:none; overf…
  • Error Line 159, Column 302: there is no attribute "allowtransparency"
    …60px; height:25px;" allowtransparency="true" frameborder="0" scrolling="no"></…

    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 172, Column 96: character "&" is the first character of a delimiter but occurred as data
    …p://sstatic1.histats.com/0.gif?1226424&101" alt="web log free" border="0"></a>…

    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 172, Column 135: end tag for "img" omitted, but OMITTAG NO was specified
    …c1.histats.com/0.gif?1226424&101" alt="web log free" border="0"></a></noscript>

    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 172, Column 44: start tag was here
    …ript><a href="http://www.histats.com"><img  src="http://sstatic1.histats.com/0…
  • Error Line 190, Column 7: end tag for "body" omitted, but OMITTAG NO was specified
    </html>

    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 65, Column 1: start tag was here
    <script src="http://megafilmeshd.net/js/modernizr.js"></script>

Visitor Analysis

Daily Visitor
  • 61.833 visits

In Page Analysis