Nonverbal and business communication: Lee Hopkins and the Better Communication Results team can help you communicate better for better business results.
Meta Keywords :
nonverbal communication, business communication, better communication, lee hopkins, australia, social media
HTTP Header reponses of leehopkins.com is the information we get when HTTP request sent to a server from connecting clients(e.g. chrome, firefox). When you input an address into your browser it sends a request to the server hosting the domain and the server responds. HTTP Header information is not directly displayed by normal web browsers like chrome, firefox etc.
HTTP/1.1 200 OK Date: Wed, 26 Feb 2014 09:12:23 GMT Server: Apache Last-Modified: Sat, 31 Aug 2013 03:30:56 GMT Accept-Ranges: bytes Content-Length: 48181 Vary: Accept-Encoding Content-Type: text/html
DNS Record Analysis
There are total 5 records in domain name system (DNS) of leehopkins.com, which includes 1 Address(A) record, 2 Name Server(NS) records, 1 Start of Authority(SOA) record and 1 Text(TXT) record.
Host Name of the node to which this record pertains
Type Type of resource record in symbolic representation.
IP/Target
TTL Count of seconds that the resource record stays valid.
Extra Info Additional resource record-specific data
leehopkins.com
A Address Record: A 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but also used for DNSBLs, storing subnet masks in RFC 1101.
66.147.242.184
14399
leehopkins.com
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns2.bluehost.com
86400
leehopkins.com
NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers.
ns1.bluehost.com
86400
leehopkins.com
SOA Start of Authority Record: Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone.
TXT Text Record: Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC DNS-SD.