Leadpages.com Website Stats

leadpages.com
(Updated 1183 days ago)
Domain : leadpages.com
Domain Title : Leadpages
WRPageWRPage : Complete In-Page SEO Analysis New Feature
WRScore WRScore(beta) is calculated on the basis of pageviews, unique visitors and unique content. :
leadpages.com Reviewed by WebRankStats on Oct 12 . Rating: Rating: 2.98 out of 10
Website IP : 216.239.38.21
Hosting Country : United States of America

Traffic Rank and Engagement

Global Rank 0
Total Visits 0
Compare with Competitors Whois Lookup DiffStats

General Information

Meta Description :
Meta Keywords :
XML Sitemap :
Robots.txt :
Gzip Compress :
Text/HTML Ratio : 10.75%

Top Search Keywords

Keyword Traffic
leadpages 27.5%
lead pages 5.7%
leadpages pricing 5.11%
leadpages templates 1.51%
leadpages login 1.47%

Website Safety

McAfee SiteAdvisor : grey visit SiteAdvisor
WOT : Unknown visit WOT

Pages Indexed

Google : visit Google
Bing : 0 visit Bing

Sociometer

Facebook Likes : 0
Stumbleupon : 0
LinkedIn : 0

Server Analysis

IP Address : 216.239.38.21
Latitude : 37.406
Longitude : -122.079
Region : Mountain View, California
Country : United States of America

HTTP Header Analysis

HTTP Header reponses of leadpages.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.0 301 Moved Permanently
Location: http://www.leadpages.com/
Content-type: text/html
X-Cloud-Trace-Context: 7d173abed311bc735f2d1c349c7b2aa7
Date: Tue, 12 Oct 2021 13:50:45 GMT
Server: Google Frontend
Content-Length: 0

HTTP/1.0 302 Found
location: https://www.leadpages.com/
X-Cloud-Trace-Context: cc3cb92e447745c6067dc5b60f8169a4
Date: Tue, 12 Oct 2021 13:50:45 GMT
Content-Type: text/html
Server: Google Frontend
Content-Length: 0
Via: 1.1 google

HTTP/1.0 200 OK
X-Frame-Options: SAMEORIGIN
Date: Tue, 12 Oct 2021 13:38:37 GMT
Expires: Tue, 12 Oct 2021 13:43:37 GMT
ETag: "_E5tpw"
X-Cloud-Trace-Context: 21f2e9ecf0abf7c01131254733702ede
Content-Type: text/html
Server: Google Frontend
Via: 1.1 google
Age: 728
Cache-Control: public, max-age=900,public, max-age=300
Content-Length: 292596
Alt-Svc: clear

DNS Record Analysis

There are total 25 records in domain name system (DNS) of leadpages.com, which includes 4 Address(A) records, 4 IPv6 Address(AAAA) records, 5 Mail Exchange(MX) records, 4 Name Server(NS) records, 1 Start of Authority(SOA) record and 7 Text(TXT) records.

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
leadpages.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. 216.239.32.21 300
leadpages.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. 216.239.38.21 300
leadpages.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. 216.239.34.21 300
leadpages.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. 216.239.36.21 300
leadpages.com AAAA IPv6 Address Record: A 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host. 300 ipv6: 2001:4860:4802:34::15
leadpages.com AAAA IPv6 Address Record: A 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host. 300 ipv6: 2001:4860:4802:36::15
leadpages.com AAAA IPv6 Address Record: A 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host. 300 ipv6: 2001:4860:4802:32::15
leadpages.com AAAA IPv6 Address Record: A 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host. 300 ipv6: 2001:4860:4802:38::15
leadpages.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. alt3.aspmx.l.google.com 300 pri: 10
leadpages.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. alt1.aspmx.l.google.com 300 pri: 5
leadpages.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. aspmx.l.google.com 300 pri: 1
leadpages.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. alt2.aspmx.l.google.com 300 pri: 5
leadpages.com MX Mail Exchange Record: Maps a domain name to a list of message transfer agents for that domain. alt4.aspmx.l.google.com 300 pri: 10
leadpages.com NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers. ns-cloud-b3.googledomains.com 21600
leadpages.com NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers. ns-cloud-b2.googledomains.com 21600
leadpages.com NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers. ns-cloud-b1.googledomains.com 21600
leadpages.com NS Name Server Record: Delegates a DNS zone to use the given authoritative name servers. ns-cloud-b4.googledomains.com 21600
leadpages.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. 21600 mname: ns-cloud-b1.googledomains.com
rname: cloud-dns-hostmaster.google.com
serial: 1
refresh: 21600
retry: 3600
expire: 259200
minimum-ttl: 300
leadpages.com 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. 300 txt: google-site-verification=ikfA5nlUnkOspuWt5zruCkjF1td92WZg8AbGoHdNG1o
entries: Array
leadpages.com 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. 300 txt: atlassian-domain-verification=oYgiGkqhDeSro8k3tUSxIla9Svj39gXqLk/a/UWDQEfOaP8cfMz09aELCB21SYVP
entries: Array
leadpages.com 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. 300 txt: ZOOM_verify_eZtHz6DmSlC13Vfd9aawEg
entries: Array
leadpages.com 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. 300 txt: MS=ms72657420
entries: Array
leadpages.com 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. 300 txt: google-site-verification=sW-nwyIQQj0xjaI40Jcu8Zs-rw2i9uP45_UsqasDLmU
entries: Array
leadpages.com 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. 300 txt: v=spf1 include:_spf.google.com include:m.dripemail2.com include:mail.zendesk.com ~all
entries: Array
leadpages.com 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. 300 txt: google-site-verification=lJPjftTO9yyHWry23prRDYpBVpycP3n8dlajkAtbAts
entries: Array

Traffic Graphs

Alexa Graph