Skip to content
https://gallup.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
0
REVIEW
5
PASS
4
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
4 PASS 5 REVIEW
B
Redirect Chain
2 redirect(s), 809 ms total
REVIEW
2 redirect(s), 809 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Redirect overhead: 809 ms total
Got: 809 ms

https://gallup.com

179 ms · HTTP/1.1

301

https://www.gallup.com/

247 ms · HTTP/1.1

301

https://www.gallup.com/home.aspx

383 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gallup.com301179 msHTTP/1.1CloudFront
2https://www.gallup.com/301247 msHTTP/1.1
3https://www.gallup.com/home.aspx200383 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 870 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 870 B Sitemaps referenced 0 User-agents amazon-kendra, GPTBot, ChatGPT-User, Claude-User, Google-Extended, cohere-ai, PetalBot, PerplexityBot, Perplexity-User, ClaudeBot, Claude-SearchBot, OAI-SearchBot, MistralAI-User, * Blocking No — crawling allowed
# Robots

User-agent: amazon-kendra

Allow: /


User-agent: GPTBot

Allow: /*.pdf$


User-agent: ChatGPT-User

Allow: /*.pdf$


User-agent: PerplexityBot

Allow: /*.pdf$


User-agent: Perplexity-User

Allow: /*.pdf$


User-agent: ClaudeBot

Allow: /*.pdf$


User-agent: Claude-User

Allow: /*.pdf$


User-agent: Claude-SearchBot

Allow: /*.pdf$


User-agent: OAI-SearchBot

Allow: /*.pdf$


User-agent: Google-Extended

Allow: /*.pdf$


User-agent: MistralAI-User

Allow: /*.pdf$


User-agent: cohere-ai

Allow: /*.pdf$


User-agent: *

Disallow: /*.gif$

Disallow: /*.png$

Disallow: /*.jpg$

Disallow: /*.jsx$

Disallow: /*.cssx$

Disallow: /*.axd$

Disallow: /*.asmx$

Disallow: /*.pdf$

Disallow: /assets/

Disallow: /dsm/

Disallow: /sorry/

Disallow: /viz/

Disallow: /shared/

Disallow: /search/

Disallow: /private/

User-agent: PetalBot

Disallow: /
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
274 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

274
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (LambdaGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: SIN2-P3)
Got: x-amz-cf-id: WCPbjj9sAkrIJaoXMmI11D5EKn4RlndQgJAJ3jTf_fbHgEnIHd57DQ==
Info::
CDN cache status: LambdaGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status LambdaGeneratedResponse from cloudfront Evidence x-amz-cf-id: WCPbjj9sAkrIJaoXMmI11D5EKn4RlndQgJAJ3jTf_fbHgEnIHd57DQ==
A
DNS Records
4 A records, 589 ms lookup
PASS
4 A records, 589 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.157.254.16, 108.157.254.44, 108.157.254.55, 108.157.254.80
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-132.awsdns-16.com, ns-1529.awsdns-63.org, ns-1602.awsdns-08.co.uk, ns-864.awsdns-44.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (589 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 589 ms
A108.157.254.16, 108.157.254.44, 108.157.254.55, 108.157.254.80
AAAA
CNAME
NSns-132.awsdns-16.com, ns-1529.awsdns-63.org, ns-1602.awsdns-08.co.uk, ns-864.awsdns-44.net
MX
10 mxb-0022c301.gslb.pphosted.com
10 mxa-0022c301.gslb.pphosted.com
TXT
4pRQ4uktU+v/e6PqZP4RCettjxpsgJ3hBFPCJ8kcv5LTZcHdB0coj29Pu3MS+DXZ31VQ7niGtGFI+k+j...
Dynatrace-site-verification=cc69d9e9-d7b3-42ca-a053-82fa08480175__ce1i60q9bp95lo...
adobe-idp-site-verification=9fb9aa11c23078a415087a53611331b84b67ebf4625f5c62baf7...
amazonses:6Ckrlls/7qIqvQb85EWeooR29nVsWMfyFPurLcSz84g=
anthropic-domain-verification-qsqfx5=WONUFQqg5K61Z1CQgzSzuu1NU
apple-domain-verification=hU6UQm0p6eLQulxr
atlassian-domain-verification=srCb9moeregJeSNI5t83q7dI3co/KRKmqUyj30unQ5BZZEW3v0...
beautifulai-site-verification=c4716ed5-0159-4a5f-a9b4-92b9813f3190
cisco-ci-domain-verification=6a346b3c3df59428813c35a3f56a2bf7881b34f1506c0d0ace5...
cursor-domain-verification-qkf7vy=EkkQ7HCuplyGgtsKlGgSDg1W0
d17bpjna9dpfai5cvuddnvee6r
docusign=f5446a7b-7410-41a4-8dad-0928ff9636fd
figma-domain-verification=244bbc44228382e6c9bd1b85052f4a8716ee181425e2f351b2cf13...
ms=ms88848829
notion-domain-verification=NBJEljfyGvBUhR1PQ4xFsCMsWhkZCJ4axCj0MC2YqWn
openai-domain-verification=dv-AOKf24FGi3AXdHQeIockVWuo
perplexity-ai-domain-verification-cxt3wq=fyCgDxrFVd6pHsslqQzy7PztR
slack-domain-verification=q0UVkYxCRe7s9ImO4SijvQQNRR1xdOHzSfx3lQBr
solarwinds-service0desk-verification=5f98167b7edc6581b77e1513093e71ee
stripe-verification=AFAD72C78A908E60A90F44BC0950387F0F52247140B809B98500F6CD6E80...
twilio-domain-verification=ba5b6045e88fa14939d9769b61766dfa
v=msv1 t=1C0DA192-E5A1-4BFD-A25A-E5630AAD4755
SPF v=spf1 ip4:198.175.140.0/24 ip4:198.175.141.0/24 ip4:199.255.192.0/22 ip4:199.12...
CAALookup not available with standard resolver
Resolved in 589 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.gallup.com/
200https://gallup.com/

Preferred variant: non-www

HTTP → HTTPS

301http://gallup.com/ https://gallup.com/

Consistent

A+
Domain Intelligence
gallup.com — via CSC Corporate Domains, Inc., 32 years, 11 months old, hosted on AWS
PASS
gallup.com — via CSC Corporate Domains, Inc., 32 years, 11 months old, hosted on AWS
Info::
Domain registered until Nov 8, 2026 (6 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

145 days

November 8, 2026

SSL certificate

274 days

Issued by Amazon

Domain age

32 years, 11 months

Registered November 9, 1993

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

108.157.254.55

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created November 9, 1993 (32 years, 11 months ago)
Expires November 8, 2026 (6 months)
Last Updated November 4, 2024
Name Servers ns-132.awsdns-16.com, ns-1529.awsdns-63.org, ns-1602.awsdns-08.co.uk, ns-864.awsdns-44.net
DNSSEC Not enabled
Hosting
IP Address 108.157.254.55
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.6s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 215 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
103 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
215 ms
Total Time Total request time from DNS lookup through full response.
216 ms

Connection waterfall

DNS Lookup 103 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 106 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback