play.google.com
Android Apps on Google Play
play.google.com is registered with MarkMonitor Inc. since September 15, 1997 (29.1 years). The registration expires on September 14, 2028. The site runs on Google Analytics 4, Universal Analytics, Google Fonts and 4 other technologies. Its email security grade is B. Its SSL certificate is issued by Google Trust Services and is valid for 51 more days.
- Domain age
- 29.1 yrs
- Technologies
- 7
- Email security
- B
- SSL days left
- 51
Registration
| Registrar | MarkMonitor Inc. |
|---|---|
| IANA ID | 292 |
| Registered | September 15, 1997 |
| Expires | September 14, 2028 |
| Updated | September 9, 2019 |
| Status | client delete prohibited, client transfer prohibited, client update prohibited, server delete prohibited, server transfer prohibited, server update prohibited |
| Name servers | ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com |
| DNSSEC | Not signed |
DNS records
| Type | Value | TTL |
|---|---|---|
| A | 142.251.155.7 | 87 |
| A | 142.251.153.7 | 87 |
| A | 142.251.157.7 | 87 |
| A | 142.251.154.7 | 87 |
| A | 142.251.150.7 | 87 |
| A | 142.251.151.7 | 87 |
| A | 142.251.156.7 | 87 |
| A | 142.251.152.7 | 87 |
| MX | alt4.gmr-smtp-in.l.google.com 40 | 600 |
| MX | alt1.gmr-smtp-in.l.google.com 10 | 600 |
| MX | alt3.gmr-smtp-in.l.google.com 30 | 600 |
| MX | alt2.gmr-smtp-in.l.google.com 20 | 600 |
| MX | gmr-smtp-in.l.google.com 5 | 600 |
| TXT | v=spf1 redirect=_spf.google.com | 600 |
| TXT | facebook-domain-verification=l3ljyvzkhsau69imdwww4eizcqgmma | 600 |
| AAAA | 2001:4860:4827:700:: | 123 |
| AAAA | 2001:4860:482d:700:: | 123 |
| AAAA | 2001:4860:482a:700:: | 123 |
| AAAA | 2001:4860:4826:700:: | 123 |
| AAAA | 2001:4860:482c:700:: | 123 |
| AAAA | 2001:4860:4828:700:: | 123 |
| AAAA | 2001:4860:4829:700:: | 123 |
| AAAA | 2001:4860:482b:700:: | 123 |
Technology stack
Analytics and advertising IDs
google_analytics:G-Q7475KZCHLgoogle_analytics:UA-19995903-1google_tag_manager:GTM-K59689FSSL certificate
| Valid | Valid |
|---|---|
| Issuer | US, WE2, Google Trust Services |
| Expires | December 31, 2026 |
| Days remaining | 51 |
| Protocol | TLSv1.3 |
| Names | *.google.com, *.appengine.google.com, *.bdn.dev, *.origin-test.bdn.dev, *.cloud.google.com, *.crowdsource.google.com, *.datacompute.google.com, *.google.ca, *.google.cl, *.google.co.in, *.google.co.jp, *.google.co.uk |
Email security
- warnNo DKIM key found at common selectors (google, selector1, selector2, default, k1, k2, s1, s2, ...). DKIM may still use a custom selector we cannot guess.
- warnNo BIMI record (optional: shows your logo next to your emails in supporting inboxes).
- goodSPF record found.
- goodSPF ends with ~all: servers you have not listed are marked as suspicious (soft fail).
- goodDMARC policy is reject: mail that fails authentication is blocked.
- goodDMARC aggregate reports are sent to mailto:[email protected].
- good1 MX record(s) found. Mail is handled by Google Workspace.
- goodMTA-STS is enforced: other servers must use verified TLS when sending you mail.
- goodTLS-RPT is set up: you receive reports about failed encrypted deliveries.
Homepage metadata
| Title | Android Apps on Google Play |
|---|---|
| Description | Enjoy millions of the latest Android apps, games, music, movies, TV, books, magazines & more. Anytime, anywhere, across your devices. |
| Language | en-US |
| Canonical | https://play.google.com/store/games?hl=en_US |
| Indexable | Yes |
| Word count | 849 |
About play.google.com
Who is the registrar of play.google.com?
play.google.com is registered with MarkMonitor Inc. (IANA ID 292).
When does play.google.com expire?
The current registration of play.google.com expires on September 14, 2028. It was first registered on September 15, 1997.
What technology does play.google.com use?
We detected 7 technologies on play.google.com, including Google Analytics 4, Universal Analytics, Google Fonts, Content Security Policy, HSTS, Google Tag Manager.
Does play.google.com protect its email with SPF and DMARC?
play.google.com scores 81/100 (grade B) for email security. No DKIM key found at common selectors (google, selector1, selector2, default, k1, k2, s1, s2, ...). DKIM may still use a custom selector we cannot guess. No BIMI record (optional: shows your logo next to your emails in supporting inboxes).