Wednesday 04 September 2013 Санал асуулга Захидал илгээх Тусламж Сурталчилгаа байрлуулах Мэдээний бичлэг Сэтгэгдлийн бичлэг Advertisement Нүүр Сексийн тухай Секс байрлал Гомо лесби бисекс Эрхтэн томруулах Эрчүүдийн асуудал Хүүхнүүдийн асуудал ... ...

cekc.mn
  • Domain Name
    cekc.mn
  • Favicon
  • Google Page Rank
    0
  • Alexa Rank
    #23048
  • Page Size
    76.5 KB
  • Ip Address
    202.170.69.24
  • Heading
    H1: 0, H2: 40, H3: 2, H4: 0, H5: 0, H6: 2
  • Images
    2 GIF, 4 JPG, 2 PNG

Website Meta Analysis

  • Title
    Секс.мн | Секс бол порно биш. Монгол эротик сэтгүүл
  • Meta Keyword
  • Meta Description
    Wednesday 04 September 2013 Санал асуулга Захидал илгээх Тусламж Сурталчилгаа байрлуулах Мэдээний бичлэг Сэтгэгдлийн бичлэг Advertisement Нүүр Сексийн тухай Секс байрлал Гомо лесби бисекс Эрхтэн томруулах Эрчүүдийн асуудал Хүүхнүүдийн асуудал ...

Technical Analysis

  • Webserver
    nginx
  • Ip Address
    202.170.69.24
  • Domain Age
  • Javascript Library
    jquery, prototype
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from cekc.mn.

HTML Analysis

  • server: nginx
  • date: Wed, 04 Sep 2013 12:16:56 GMT
  • content-type: text/html; charset=UTF-8
  • content-length: 15578
  • connection: keep-alive
  • vary: Accept-Encoding, Cookie
  • cache-control: max-age=3, must-revalidate
  • wp-super-cache: Served supercache file from PHP
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for cekc.mn

DNS Analysis


DNS servers
ns1.dot.mn [202.170.69.12]
ns2.dot.mn [202.170.69.12]


DNS Records

Answer records
cekc.mn MX
preference: 30
exchange: aspmx4.googlemail.com
10800s
cekc.mn MX
preference: 30
exchange: aspmx5.googlemail.com
10800s
cekc.mn MX
preference: 10
exchange: aspmx.l.google.com
10800s
cekc.mn MX
preference: 20
exchange: alt1.aspmx.l.google.com
10800s
cekc.mn MX
preference: 20
exchange: alt2.aspmx.l.google.com
10800s
cekc.mn MX
preference: 30
exchange: aspmx2.googlemail.com
10800s
cekc.mn MX
preference: 30
exchange: aspmx3.googlemail.com
10800s
cekc.mn A 202.170.69.24 10800s
cekc.mn NS  ns2.dot.mn 10800s
cekc.mn NS  ns1.dot.mn 10800s
cekc.mn SOA
server: ns1.dot.mn
email: tech@datacom.mn
serial: 2010110101
refresh: 43200
retry: 7200
expire: 604800
minimum ttl: 86400
1500s

Authority records

Additional records
ns1.dot.mn A 202.170.69.12 10800s
ns2.dot.mn A 202.170.69.12 10800s

IP 202.170.69.24 Analysis

  • Country Code
    MN
  • Country Code3
    MNG
  • Country Name
    Mongolia
  • City
    Ulaanbaatar
  • Continent Code
    AS
  • Latitude
    47.9167
  • Longitude
    106.9167
  • % [whois.apnic.net node-6]
    % Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

    inetnum: 202.170.64.0 - 202.170.95.255
    netname: MONGOLNET
    descr: Bodicomputer Co.,ltd.
    descr: Ulaanbaatar,MONGOLIA
    country: MN
    admin-c: AC71-AP
    tech-c: AB18-AP
    mnt-by: APNIC-HM
    mnt-lower: MAINT-MN-BODICOM
    mnt-routes: MAINT-MN-BODICOM
    changed: hostmaster@apnic.net 19990609
    status: ALLOCATED PORTABLE
    changed: hm-changed@apnic.net 20071008
    changed: hm-changed@apnic.net 20091211
    source: APNIC

    route: 202.170.69.0/24
    descr: BODICOM
    origin: AS45237
    mnt-by: MAINT-MN-BODICOM
    changed: bataa@magicnet.mn 20091223
    source: APNIC

    person: Avaadorj Choijoo
    address: Sukhbaatar square-3, Central Cultural Palace,
    address: 12-th floor, Ulaanbaatar 11/20A, Mongolia.
    country: MN
    phone: +976-1-310639
    fax-no: +976-1-312307
    e-mail: avaadorj@mongolnet.mn
    nic-hdl: AC71-AP
    mnt-by: ALT-GRL
    changed: hostmaster@apnic.net 19990216
    source: APNIC

    person: Altangerel Bayar
    address: Sukhbaatar square-3, Central Cultural Palace,
    address: 12-th floor, Ulaanbaatar 11/20A, Mongolia.
    country: MN
    phone: +976-1-310639
    fax-no: +976-1-312307
    e-mail: altangerelb@mongolnet.mn
    nic-hdl: AB18-AP
    mnt-by: ALT-GRL
    changed: hostmaster@apnic.net 19990216
    source: APNIC


In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 29 Errors
  • 7 Warnings
Ratio Text/Html
  • 0.7851906720134862
Message Error
  • Error Line 2, Column 74: there is no attribute "prefix"
    …/www.w3.org/1999/xhtml" dir="ltr" lang="mn-MN" prefix="og: http://ogp.me/ns#" >

    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 42, Column 50: there is no attribute "property"
    …oker generated tags --><meta property="og:locale" content="mn_MN" /> <meta pro…

    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 400, Column 207: there is no attribute "src"
    …ptAccess" value="always" /><embed src="http://www.dailymotion.com/swf/xad852" …

    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 400, Column 265: there is no attribute "allowscriptaccess"
    …ion.com/swf/xad852" allowscriptaccess="always" allowfullscreen="true" width="3…

    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 400, Column 290: there is no attribute "allowfullscreen"
    …scriptaccess="always" allowfullscreen="true" width="300" height="220"></embed>…

    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 400, Column 303: there is no attribute "width"
    …cess="always" allowfullscreen="true" width="300" height="220"></embed></object>

    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 400, Column 316: there is no attribute "height"
    …cess="always" allowfullscreen="true" width="300" height="220"></embed></object>

    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 400, Column 321: element "embed" undefined
    …cess="always" allowfullscreen="true" width="300" height="220"></embed></object>

    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 404, Column 321: element "embed" undefined
    …cess="always" allowfullscreen="true" width="300" height="220"></embed></object>

    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 524, Column 96: there is no attribute "border"
    …w.acaa.mn/8366-2"><img src="http://www.cekc.mn/acaa300x500.jpg" border="0"></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 524, Column 99: required attribute "alt" not specified
    …w.acaa.mn/8366-2"><img src="http://www.cekc.mn/acaa300x500.jpg" border="0"></a>

    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 524, Column 103: end tag for "img" omitted, but OMITTAG NO was specified
    …w.acaa.mn/8366-2"><img src="http://www.cekc.mn/acaa300x500.jpg" border="0"></a>

    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 524, Column 43: start tag was here
    …v><a href="http://www.acaa.mn/8366-2"><img src="http://www.cekc.mn/acaa300x500…

Visitor Analysis

Daily Visitor
  • 4.433 visits