myhomemsn.com

Learn how to make MSN your homepage with these easy steps. Set your homepage to MSN in just a few seconds. ...

Display Widget for this domain on your website. Click Here
This data was last updated from 15-07-2013 09:47:41  (update).

Overview Info

  • Domain Name
    myhomemsn.com
  • Favicon
  • Alexa Rank
    #18568
  • Google Page Rank
    PR 6
  • Ip Address
    131.253.13.140
  • Page Size
    30.2 KB
  • Images
    1 GIF, 5 JPG, 4 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    4 4 1 1 0 0

Website Meta Analysis



  • Title
    Make MSN My Homepage – How to Change Homepage Settings
  • Meta Keyword
    Make MSN your homepage, make this my homepage, change homepage, set homepage, how to change homepage, MSN, Microsoft MSN, set MSN homepage, set MSN my homepage, homepage MSN, set homepage MSN Microsoft, set homepage to MSN, set MSN as homepage, make MSN your homepage, change your homepage, how to change your homepage, set your homepage, make this your homepage, MSN home page, MSN homepage, Microsoft MSN, Microsoft, set MSN as your homepage, set homepage MSN
  • Meta Description
    Learn how to make MSN your homepage with these easy steps. Set your homepage to MSN in just a few seconds.

Technical Analysis



  • Webserver
  • Ip Address
    131.253.13.140
  • Domain Age
    5 Years, 7 Months, 2 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

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

HTML Analysis

  • cache-control: no-cache, no-store
  • pragma: no-cache
  • content-type: text/html; charset=utf-8
  • content-encoding: gzip
  • expires: -1
  • x-frame-options: DENY
  • x-content-type-options: nosniff
  • x-aspnet-version: 4.0.30319
  • p3p: CP="NON UNI COM NAV STA LOC CURa DEVa PSAa PSDa OUR IND"
  • content-length: 6656
  • date: Mon, 15 Jul 2013 09:47:40 GMT
  • connection: keep-alive
  • vary: Accept-Encoding
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
Registrant:
Domain Administrator
Microsoft Corporation
One Microsoft Way
Redmond WA 98052
US
email +1.4258828080 Fax: +1.4259367329

Domain Name: myhomemsn.com

Registrar Name: Markmonitor.com
Registrar Whois: whois.markmonitor.com
Registrar Homepage: http://www.markmonitor.com

Administrative Contact:
Domain Administrator
Microsoft Corporation
One Microsoft Way
Redmond WA 98052
US
email +1.4258828080 Fax: +1.4259367329
Technical Contact, Zone Contact:
MSN Hostmaster
Microsoft Corporation
One Microsoft Way
Redmond WA 98052
US
email +1.4258828080 Fax: +1.4259367329

Created on..............: 2007-12-12.
Expires on..............: 2013-12-12.
Record last updated on..: 2012-06-23.

Domain servers in listed order:

ns1.msft.net
ns5.msft.net
ns4.msft.net
ns3.msft.net
ns2.msft.net

DNS Analysis


DNS servers
ns3.msft.net [213.199.180.53]
ns1.msft.net [65.55.37.62]
ns5.msft.net [65.55.226.140]
ns2.msft.net [64.4.59.173]
ns4.msft.net [207.46.75.254]

DNS Records

Answer records
myhomemsn.com A 131.253.13.140 3600s
myhomemsn.com NS  ns2.msft.net 172800s
myhomemsn.com NS  ns3.msft.net 172800s
myhomemsn.com NS  ns4.msft.net 172800s
myhomemsn.com NS  ns1.msft.net 172800s
myhomemsn.com NS  ns5.msft.net 172800s
myhomemsn.com SOA
server: ns1.msft.net
email: msnhst@microsoft.com
serial: 2012100101
refresh: 1800
retry: 900
expire: 2419200
minimum ttl: 3600
86400s

Authority records

Additional records
ns2.msft.net A 64.4.59.173 3600s
ns2.msft.net 28 [16 bytes] 3600s
ns3.msft.net A 213.199.180.53 3600s
ns3.msft.net 28 [16 bytes] 3600s
ns4.msft.net A 207.46.75.254 3600s
ns4.msft.net 28 [16 bytes] 3600s
ns1.msft.net A 65.55.37.62 3600s
ns1.msft.net 28 [16 bytes] 3600s
ns5.msft.net A 65.55.226.140 3600s
ns5.msft.net 28 [16 bytes] 3600s

IP 131.253.13.140 Analysis

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

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 15 Errors
  • 9 Warnings
Ratio Text/Html
  • 0.3555045129565527
Message Error
  • Error Line 21, Column 21: there is no attribute "ID"
        <ie:homePage ID="oHomePage" style="behavior:url(#default#homepage);"> </ie:…

    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 21, Column 39: there is no attribute "style"
        <ie:homePage ID="oHomePage" style="behavior:url(#default#homepage);"> </ie:…

    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 21, Column 73: element "ie:homePage" undefined
    …omePage ID="oHomePage" style="behavior:url(#default#homepage);"> </ie:homePage>

    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 27, Column 183: there is no attribute "bi:events"
    …in_0_content_0_ctl05_aLink" bi:events="event1,event13" bi:atlasview="" bi:link…

    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 27, Column 213: there is no attribute "bi:atlasview"
    …:events="event1,event13" bi:atlasview="" bi:linkname="Go to MSN" class="msn-lo…

    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 27, Column 228: there is no attribute "bi:linkname"
    …,event13" bi:atlasview="" bi:linkname="Go to MSN" class="msn-logo show-end"><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 38, Column 173: there is no attribute "bi:linktype"
    …me="Main CTA:Treatment A" bi:linktype="o" bi:prop9="MSN DHP:Treatment A" bi:ev…

    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 38, Column 186: there is no attribute "bi:prop9"
    …Treatment A" bi:linktype="o" bi:prop9="MSN DHP:Treatment A" bi:evar9="MSN DHP:…

    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 38, Column 217: there is no attribute "bi:evar9"
    …:prop9="MSN DHP:Treatment A" bi:evar9="MSN DHP:Treatment A" class="button-gree…

    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 138, Column 73: required attribute "alt" not specified
                            <img id="main_0_content_0_imgThanksImg" src="" />

    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 198, Column 239: required attribute "alt" not specified
    …rmdefaultsnewprod/1/H.24.3--NS/0" height="1" width="1" border="0" /></noscript>

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

  • Warning Line 458, Column 35: character "&" is the first character of a delimiter but occurred as data
          if (typeof $ != "undefined" && typeof $.bi != "undefined") {

    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 458, Column 36: character "&" is the first character of a delimiter but occurred as data
          if (typeof $ != "undefined" && typeof $.bi != "undefined") {

    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.

Visitor Analysis

Daily Visitor
  • 8.167 visits

In Page Analysis