cia.gov

Central Intelligence Agency

​

If you are the owner of this website, please login to edit the contents.

Content Analysis

cia.gov has Alexa Rank 10.365 and Google Page Rank is 8

Title

Welcome to the CIA Web Site — Central Intelligence Agency

Page Size

31.3 KB

Meta Keywords

Images

  • 0 GIF, 0 JPG, 0 PNG

Heading

  • H1: 1, H2: 0, H3: 3, H4: 0, H5: 0, H6: 0

Meta Description

Central Intelligence Agency

Visitor Analysis

Daily Visitor

  • 13.417 visits

Visitor Contry Map

DNS Record Analysis

The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. A Domain Name Service resolves queries for these names into IP addresses for the purpose of locating computer services and devices worldwide. By providing a worldwide, distributed keyword-based redirection service, the Domain Name System is an essential component of the functionality of the Internet.



DNS servers
relay1.ucia.gov [198.81.129.193]
relay7.ucia.gov [198.81.129.186]


DNS Records

Answer records
cia.gov TXT v=spf1 mx a:mail1a.cia.gov a:mail1b.cia.gov a:mail2a.cia.gov a:mail2b.cia.gov mx:cia.gov mx:ucia.gov ~all 900s
cia.gov MX
preference: 10
exchange: mail2.cia.gov
900s
cia.gov MX
preference: 20
exchange: mail1.cia.gov
900s
cia.gov A 198.81.129.107 900s
cia.gov SOA
server: relay7.ucia.gov
email: monrpt@ucia.gov
serial: 2012110600
refresh: 7200
retry: 3600
expire: 2419200
minimum ttl: 900
900s
cia.gov NS  relay2.ucia.gov 900s
cia.gov NS  relay1.ucia.gov 900s
cia.gov NS  relay12.ucia.gov 900s
cia.gov NS  relay7.ucia.gov 900s

Authority records

Additional records
mail2.cia.gov A 198.81.129.148 900s
mail1.cia.gov A 198.81.129.68 900s
relay1.ucia.gov A 198.81.129.193 14400s
relay2.ucia.gov A 198.81.129.194 14400s
relay7.ucia.gov A 198.81.129.186 14400s
relay12.ucia.gov A 198.81.129.195 14400s

Traffic Analysis

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

Http Header Analysis

Hyper Text Transfer Protocol (HTTP) header show data header response from cia.gov .

HTML Analysis

  • etag: "67b4a37a3f94c22404601715b295b23e:1369935183"
  • last-modified: Thu, 30 May 2013 17:30:17 GMT
  • accept-ranges: bytes
  • content-type: text/html
  • vary: Accept-Encoding
  • content-encoding: gzip
  • content-length: 7843
  • date: Tue, 04 Jun 2013 08:21:33 GMT
  • connection: keep-alive
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Site Technical Analysis

Web server

Javascript Library

  • jquery

Ip Address

Language used

  • HTML
  • CSS
  • JAVASCRIPT

Domain Age

Check speed

Site same Ip 198.81.129.107(View more...)

Whois Analysis

Whois Data

(View more...) % DOTGOV WHOIS Server ready
Domain Name: CIA.GOV
Status: ACTIVE


>>> Last update of whois database: Sun, 30 Sep 2012 11:05:15 UTC


Whois Ip

(View more...) ANS Communications, Inc BLK198-15-ANS (NET-198-80-0-0-1) 198.80.0.0 - 198.81.255.255
Central Intelligence Agency OIT-BLK1 (NET-198-81-128-0-1) 198.81.128.0 - 198.81.191.255

Check Speed Analysis

Summary

Document Complete Fully Loaded
Load Time First Byte Start Render DOM Elements Time Requests Bytes In Time Requests Bytes In
First View 5.410s 1.318s 2.007s 482 5.410s 63 837 KB 6.441s 64 838 KB
Repeat View 1.850s 0.530s 1.149s 482 1.850s 63 17 KB 1.939s 64 17 KB

First View Repeat View
Waterfall

Content Breakdown

Content breakdown by MIME type (First View)

Connection View


Content breakdown by MIME type (Repeat View)

Connection View (Repeat View)


HTML Analysis

HTML validation

  • 9 Errors
  • 12 Warnings

Ratio Text/Html

  • 0.546834101956874

Message Error

(View more...)
  1. Warning Line 521, Column 127: character "&" is the first character of a delimiter but occurred as data 
    …nformation"><span class='imea imeam'><span></span></span>News & Information</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.
  2. Warning Line 758, Column 170: character "&" is the first character of a delimiter but occurred as data 
    …1;ulm_strict=(dcm=document.compatMode)&&dcm=="CSS1Compat";if((ulm_ie&&!(ulm_ie…

    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.
  3. Warning Line 758, Column 172: cannot generate system identifier for general entity "dcm" 
    …ulm_strict=(dcm=document.compatMode)&&dcm=="CSS1Compat";if((ulm_ie&&!(ulm_ie7&…

    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.

  4. Error Line 758, Column 172: general entity "dcm" not defined and no default entity 
    …ulm_strict=(dcm=document.compatMode)&&dcm=="CSS1Compat";if((ulm_ie&&!(ulm_ie7&…

    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.

  5. Warning Line 758, Column 175: reference not terminated by REFC delimiter 
    …_strict=(dcm=document.compatMode)&&dcm=="CSS1Compat";if((ulm_ie&&!(ulm_ie7&&ul…

    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.

  6. Error Line 758, Column 175: reference to entity "dcm" for which no system identifier could be generated 
    …_strict=(dcm=document.compatMode)&&dcm=="CSS1Compat";if((ulm_ie&&!(ulm_ie7&&ul…

    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.

Processing update domain...