Skip to content
https://life360.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1761 ms total
FIX
2 redirect(s), 1761 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::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.life360.com:443/
Warning::
Redirect overhead: 1761 ms total
Got: 1761 ms
Info::
Cross-domain redirect detected

https://life360.com

1103 ms · HTTP/1.1

301

https://www.life360.com:443/

232 ms · HTTP/1.1

302

https://intl.life360.com

426 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://life360.com3011103 msHTTP/1.1awselb/2.0
2https://www.life360.com:443/302232 msHTTP/1.1cloudflare
3https://intl.life360.com200426 msHTTP/1.1cloudflare

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
HTTP Probe Timing
Total 1057 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
99 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
239 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
480 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.06 s
Total Time Total request time from DNS lookup through full response.
1.06 s

Connection waterfall

DNS Lookup 99 ms TCP Connect 239 ms TLS Handshake 480 ms Server Processing 239 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
116 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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
A
DNS Records
2 A records, 591 ms lookup
PASS
2 A records, 591 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 44.213.168.186, 3.81.251.116
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1213.awsdns-23.org, ns-1612.awsdns-09.co.uk, ns-510.awsdns-63.com, ns-952.awsdns-55.net
Info::
9 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 (591 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 591 ms
A44.213.168.186, 3.81.251.116
AAAA
CNAME
NSns-1213.awsdns-23.org, ns-1612.awsdns-09.co.uk, ns-510.awsdns-63.com, ns-952.awsdns-55.net
MX
10 mxa-0096d201.gslb.pphosted.com
10 mxb-0096d201.gslb.pphosted.com
100 aspmx3.googlemail.com
100 aspmx2.googlemail.com
100 aspmx4.googlemail.com
100 aspmx.l.google.com
100 aspmx5.googlemail.com
100 alt1.aspmx.l.google.com
100 alt2.aspmx.l.google.com
TXT
06yfvdllkqsp7v0klwynlswzfcbl2y3t
MS=ms34567318
airalo-domain-verification=N8xdM2x8mpU0Ij3
airtable-verification=20c2c5b54c0582f292b726e91de775d8
amazon-business-verification=7ef9abe879ed10c80c0849097bcc9bd41a27c87fc5cc73d21f3...
anthropic-domain-verification-mcmgzw=4qb6T6ZaxdCojITG5U58peM5r
applause-verification:de202bf5-13b3-4ff6-861c-d97eb97f002e
apple-domain-verification=y1mrQeApW3De4DWC
atlassian-domain-verification=zV/LomqWsGtSYc3ihXHKoL2/1JFNRJzZ8vt87JB/Lj093hu4dS...
atlassian-sending-domain-verification=ea1af3f1-e876-45fb-97e6-743590f24dd1
box-domain-verification=de06409315acff6cf2054146880981869f835106c3699e6f9bb6b053...
ca3-2e480410e8ca43a89b460141e3381679
ca3-76e6ae8f8c8947999922cbe76ba5cd1e
cnvhd6qupgdk40f0kb28v72mpd
cursor-domain-verification-m2nzc9=aaP1P9xfeC48GAzt9sVzkLfTL
docker-verification=0dcde763-da47-428f-ba31-a0016912fbc3
docusign=b92a5575-5277-4bd6-a807-09f1bb0ac27d
dropbox-domain-verification=ypfw1blj6d47
facebook-domain-verification=fntzimb5g0vv6g0kyb70teaubgoz2e
gc-ai-domain-verification-ge49ff=Sharoe9vOl748C7CFZvhqfnnd
google-site-verification:JX0ot8AD9wR8fvz-gQg9Y61fTk9Vk0Eg6OOZkOzNhyg
google-site-verification:essv4ndzi1sfKkAKE36ZFmFk-EsZfDDFYytbDg7tD_s
google-site-verification=HIKD7oStmSRMpMRkI68V277654sgKklnQPGI3nGXvv4
google-site-verification=eX0tTU1pPW3JdMLqoihBp1pzW4iYeyq8pG9vSvbN8w8
google-site-verification=qdK-hmJnrfQ14V2izW01zFoLpbxs31S_LznkWyZ2n6k
google-site-verification=uFr3k-iMxmE1k2umPhGOY51FWhMJBicqnF9HpEj5j8Q
h1-domain-verification=xBNkD3rEZZQREqdKVnD75urn3bhxTePPz3yDhdykwKzwKHfN
have-i-been-pwned-verification=c1a9f0346363caa63b2fe22ff24e5953
hubspot-domain-verification=NjlmMmZmYzctMjE1NC00ZGE3LWEzMjgtNjczNDg5ZTdlMDE3
jetbrains-domain-verification=9zsv6hieszokr6lgk0a5s8k7z
knowbe4-site-verification=b0c3de1f7e3a86e500759e7adcab6d29
notion-domain-verification=OuKPV9sYxGs4Zs72xRkOBeMhQawOwpaRBOLFyvkOvOK
openai-domain-verification=dv-srVKcnaUq9xDEhxrKRfpRmdO
parallels-domain-verification=a364e7cd440d4ec3b00b1059f2e41a4bd53e993577494b15ad...
postman-domain-verification=985cac088d62feb06dd84c90ab5b912184237b83df1d5d1aa19a...
rube-domain-verification-gpdpqz=NlLdOtktblROvDDPxYMF0junJ
slack-domain-verification=zUbmGH133bkqFwv6hkejh9DgRoSsR9knvvXvAsuT
stripe-verification=9294826f0afafbe816d9b7b0813491234ee1fa48e649907bea97b078e72e...
stripe-verification=b4c43f5b509ff7e3270fd451d7b6baaefcd6d20e11858a45a1486cb9e078...
stripe-verification=dd3c78ad437df1fd5e0b6892ecb9880613f3fd3857f9351cb4c65dce7f53...
teamviewer-sso-verification=1f3f12b02b1e4f01a41db0671ef951c6
uber-domain-verification=636ec603-6486-4ca6-bab7-be0e5eaae954
SPF v=spf1 ip4:66.159.240.76 ip4:66.159.238.49 include:amazonses.com include:sendgri...
whimsical=4a674b8cfc6a8c8029bf29c07fdcb1d87e3812cc
wiz-domain-verification=2a8f79d2ef843b24514b2325b32871261c5599782a0ef8e43a1ed1a7...
CAALookup not available with standard resolver
Resolved in 591 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+
Crawlability
robots.txt present, sitemap with 102 URLs
PASS
robots.txt present, sitemap with 102 URLs
Info::
robots.txt is present
Got: 2599 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 102 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2599 B Sitemaps referenced 38 User-agents GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, Bingbot, * Blocking No — crawling allowed
# *
User-agent: *
Allow: /
Disallow: /*?*utm_
Disallow: /*?*gclid=
Disallow: /*?*fbclid=
Disallow: /*?*msclkid=
Disallow: /*?*ttclid=
Disallow: /*?*dclid=
Disallow: /*?*wbraid=
Disallow: /*?*gbraid=

# GPTBot
User-agent: GPTBot
Allow: /

# ChatGPT-User
User-agent: ChatGPT-User
Allow: /

# ClaudeBot
User-agent: ClaudeBot
Allow: /

# PerplexityBot
User-agent: PerplexityBot
Allow: /

# Google-Extended
User-agent: Google-Extended
Allow: /

# Bingbot
User-agent: Bingbot
Allow: /

# Host
Host: https://www.life360.com

# Sitemaps
Sitemap: https://www.life360.com/sitemap-en-us.xml
Sitemap: https://www.life360.com/sitemap-en-ca.xml
Sitemap: https://www.life360.com/sitemap-en-au.xml
Sitemap: https://www.life360.com/sitemap-en-nz.xml
Sitemap: https://www.life360.com/sitemap-en-gb.xml
Sitemap: https://www.life360.com/sitemap-en-eu.xml
Sitemap: https://www.life360.com/sitemap-en-be.xml
Sitemap: https://www.life360.com/sitemap-en-fi.xml
Sitemap: https://www.life360.com/sitemap-en-at.xml
Sitemap: https://www.life360.com/sitemap-en-fr.xml
Sitemap: https://www.life360.com/sitemap-en-ie.xml
Sitemap: https://www.life360.com/sitemap-en-de.xml
Sitemap: https://www.life360.com/sitemap-de-de.xml
Sitemap: https://www.life360.com/sitemap-en-nl.xml
Sitemap: https://www.life360.com/sitemap-nl-nl.xml
Sitemap: https://www.life360.com/sitemap-sv-se.xml
Sitemap: https://www.life360.com/sitemap-fi-fi.xml
Sitemap: https://www.life360.com/sitemap-no-no.xml
Sitemap: https://www.life360.com/sitemap-da-dk.xml
Sitemap: https://www.life360.com/server-sitemap-en-us.xml
Sitemap: https://www.life360.com/server-sitemap-en-ca.xml
Sitemap: https://www.life360.com/server-sitemap-en-au.xml
Sitemap: https://www.life360.com/server-sitemap-en-nz.xml
Sitemap: https://www.life360.com/server-sitemap-en-gb.xml
Sitemap: https://www.life360.com/server-sitemap-en-eu.xml
Sitemap: https://www.life360.com/server-sitemap-en-be.xml
Sitemap: https://www.life360.com/server-sitemap-en-fi.xml
Sitemap: https://www.life360.com/server-sitemap-en-at.xml
Sitemap: https://www.life360.com/server-sitemap-en-fr.xml
Sitemap: https://www.life360.com/server-sitemap-en-ie.xml
Sitemap: https://www.life360.com/server-sitemap-en-de.xml
Sitemap: https://www.life360.com/server-sitemap-de-de.xml
Sitemap: https://www.life360.com/server-sitemap-en-nl.xml
Sitemap: https://www.life360.com/server-sitemap-nl-nl.xml
Sitemap: https://www.life360.com/server-sitemap-sv-se.xml
Sitemap: https://www.life360.com/server-sitemap-fi-fi.xml
Sitemap: https://www.life360.com/server-sitemap-no-no.xml
Sitemap: https://www.life360.com/server-sitemap-da-dk.xml
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

302https://www.life360.com/
200https://life360.com/

Preferred variant: non-www

HTTP → HTTPS

301http://life360.com/ https://life360.com:443/

Consistent

A+
Domain Intelligence
life360.com — via Amazon Registrar, Inc., 24 years, 7 months old, hosted on AWS
PASS
life360.com — via Amazon Registrar, Inc., 24 years, 7 months old, hosted on AWS
Info::
Domain registered until Jan 12, 2027 (8 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: Amazon Registrar, 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: AS14618
Domain expiry

182 days

January 12, 2027

SSL certificate

116 days

Issued by Amazon

Domain age

24 years, 7 months

Registered January 12, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

44.213.168.186

Registrar

Amazon Registrar, 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 Amazon Registrar, Inc.
Created January 12, 2002 (24 years, 7 months ago)
Expires January 12, 2027 (8 months)
Last Updated December 8, 2025
Name Servers ns-1213.awsdns-23.org, ns-1612.awsdns-09.co.uk, ns-510.awsdns-63.com, ns-952.awsdns-55.net
DNSSEC Not enabled
Hosting
IP Address 44.213.168.186
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.8s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback