lyft.com
The domain lyft.com answers at IP address 13.226.244.96. The domain DNS is managed by Amazon Route 53, which decides where each subdomain points. Mail for lyft.com goes through 5 servers; the highest priority one is aspmx.l.google.com. It also publishes 38 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
A A records
- 13.226.244.96 60s
- 13.226.244.105 60s
- 13.226.244.39 60s
- 13.226.244.26 60s
MX MX records
- 1 aspmx.l.google.com 300s
- 5 alt1.aspmx.l.google.com 300s
- 5 alt2.aspmx.l.google.com 300s
- 10 alt4.aspmx.l.google.com 300s
- 10 alt3.aspmx.l.google.com 300s
NS NS records
- ns-288.awsdns-36.com 21446s
- ns-973.awsdns-57.net 21446s
- ns-1656.awsdns-15.co.uk 21446s
- ns-1254.awsdns-28.org 21446s
TXT TXT records
- google-site-verification=PqR4kCoyX0mHFS9nEVXAOsciOi7cGmFWXZqwR0V9k84 300s
- 5trd58kv8qzr10f1p29pzvy7q37962jd 300s
- anthropic-domain-verification-tqdk4f=P0qyx4vCYbcuEXC6m08kjNlBK 300s
- google-site-verification=Llh0du3vyHszBXJmJePgz_0i_SH4F30IfVz55ni5EJU 300s
- zapier-domain-verification-challenge=899d6325-8867-4fca-9eaf-1467d03dc839 300s
- docusign=c728f1c4-55eb-448f-8f78-343ccabebf24 300s
- twilio-domain-verification=4ddcb4bd13c31634ec2b930b65758976 300s
- autodesk-domain-verification=k3JjbSmuInr6IfRlgz_L 300s
- cursor-domain-verification-2nqeqb=vSwAwSQDJLMNl3kyYLA4lwXiH 300s
- atlassian-sending-domain-verification=de432ac6-218d-47e0-ae0d-762c47fffc44 300s
- DirectFedAuthUrl=https://lyft.okta.com/app/lyft_verinttestnew_1/exkwuie3g81ARphvu1t7/sso/saml 300s
- google-site-verification=I_p-2eYnzvWHvYp_tAsaGVvrC8de0I5_9NQewIC8vzo 300s
- apple-domain-verification=LbkM8uyQIL6BFrkd 300s
- google-site-verification=V9fk-oLTj9Ewu7Kc6Vetf94qp8HZ3gfjxFMkn8LmZ3Y 300s
- lovable_verification=654b135faa8f86fb58ca3254be8ada55459e6c69c070d57e5f7f436d21f6b001 300s
- infoblox-domain-mastery=9cd50d5c64b2ffd6d66562915d4ce9a17c37622544507534f71133ec5b01a66fa7 300s
- adobe-idp-site-verification=966b340b4edd6859f304fee5ff8977b2c7d4bf45dd1d625d3dfa67b76b508354 300s
- google-site-verification=32agu48SsNwrbzTil2TaRoTQSHglB4ovQfrUIvNMp9U 300s
- ecostruxure-it-verification=13c4c2b2-33ef-4f97-bff6-ff0c9b8b90c5 300s
- atlassian-domain-verification=glvGFizVc31XNv8C4rHe8t1rQabKIO1Tsq0kqHziwOhuoNvLKQ07KOVbT7Gq9dLa 300s
- google-site-verification=nhYLdh8rFg31IFcp5kYO14XHey2DScX8iNdKvl37chQ 300s
- google-site-verification=WhOYNvBx87wMtBZZIA-_mDjxz59lpr85v5WXEe95GiU 300s
- pendo-domain-verification=sGMonV4s-meenG0YD0p9Y2EEpqk 300s
- google-site-verification=yJG5wmMb17hGbdIRmgb908LjNkSGlhQdAKxRaI0nmWw 300s
- ZOOM_verify_vvYcalasSF-WfUCSv1dudA 300s
- atlassian-domain-verification=kM7o6XSbESYL/hqvf2XCi1b0hiFNS+ydr5EUW/fI3risMi2W1slVFEqDqItXzmNg 300s
- _ohbh9gfx8y7rjwyqxoly0m21khvr6dz 300s
- openai-domain-verification=dv-ePkUxGIu6BZWAX1ejHCQXxop 300s
- parallels-domain-verification=a5ba84c7e2a3444f991cce4e3aa4223614268698e5e1401e9b9556366af16c00 300s
- jamf-site-verification=r_dCj-trsthX0s_MKl3TBw 300s
- astro-domain-verification=cm20oaz701hbe01jldll8d78o 300s
- verification_token=lUpQbAa0BNNaVg9cINkzpJeLp 300s
- google-site-verification=mFVJm3TWDwwvPm8TVoIfJn1hLnh6jhe_LOLopOdPnOM 300s
- v=spf1 include:qemailserver.com include:docebosaas.com include:_spf.google.com include:mailgun.org include:amazonses.com include:mail.zendesk.com include:spf_c.oraclecloud.com include:usermail.zohocreator.com include:_spf.salesforce.com -all 300s
- airtable-verification=f58920465bf1b2441a1de42947f04eae 300s
- stripe-verification=ff8b9bef39bd1aec7a337faae1a557b5244999f27f887d9fdf526c65e8c1a242 300s
- MS=ms66164867 300s
- dropbox-domain-verification=k0y5aonn2ngq 300s
SOA SOA records
- ns-288.awsdns-36.com 900s
What each record means
- A and AAAA: the server IP address, in IPv4 and IPv6.
- MX: the servers that receive the domain mail. The number is the priority; the lowest is tried first.
- NS: the name servers, which have the final say over the domain DNS.
- TXT: free text. Mostly used for SPF, DKIM and DMARC, and to verify ownership with third parties.
- TTL: how many seconds the record may be cached before asking again.
Checked 3 hours ago.