| f | Skip to main content | f | Skip to main content |
| | | |
| Google Workspace Admin Help | | Google Workspace Admin Help |
| | | |
| Sign in | | Sign in |
| | | |
| Google Help | | Google Help |
| | | |
| * Help Center | | * Help Center |
| * Community | | * Community |
| * Google Workspace Admin | | * Google Workspace Admin |
| | | |
| * Privacy Policy | | * Privacy Policy |
| * Terms of Service | | * Terms of Service |
| * Submit feedback | | * Submit feedback |
| | | |
| Send feedback on... | | Send feedback on... |
| | | |
| This help content & information | | This help content & information |
| | | |
| General Help Center experience | | General Help Center experience |
| | | |
| Next | | Next |
| | | |
| * Help Center | | * Help Center |
| * Community | | * Community |
| * | | * |
| | | |
| Google Workspace Admin | | Google Workspace Admin |
| | | |
| * Contact support / fix a problem | | * Contact support / fix a problem |
| * Fix a problem | | * Fix a problem |
| * Gmail issues | | * Gmail issues |
| * Problems with sending | | * Problems with sending |
| * Email sender guidelines | | * Email sender guidelines |
| | | |
| Notification | | Notification |
| | | |
| Duet AI is now Gemini for Google Workspace. Learn more | | Duet AI is now Gemini for Google Workspace. Learn more |
| | | |
| # Email sender guidelines | | # Email sender guidelines |
| | | |
| The guidelines in this article can help you successfully send and | | The guidelines in this article can help you successfully send and |
| deliver | | deliver |
| email to personal Gmail accounts. Starting in 2024, email senders | | email to personal Gmail accounts. Starting in 2024, email senders |
| must meet | | must meet |
| the requirements described here to send email to Gmail personal a | | the requirements described here to send email to Gmail personal a |
| ccounts. A | | ccounts. A |
| personal Gmail account is an account that ends in @gmail.com or | | personal Gmail account is an account that ends in @gmail.com or |
| @googlemail.com. | | @googlemail.com. |
| | | |
| For the latest updates about sender requirements, visit the Email | | For the latest updates about sender requirements, visit the Email |
| sender | | sender |
| guidelines FAQ. | | guidelines FAQ. |
| | | |
| **Google Workspace senders:** If you use Google Workspace to send | | **Google Workspace senders:** If you use Google Workspace to send |
| large | | large |
| volumes of email, review the Spam and abuse policy in Gmail. The | | volumes of email, review the Spam and abuse policy in Gmail. The |
| policy is | | policy is |
| part of the Google Workspace Acceptable Use Policy. | | part of the Google Workspace Acceptable Use Policy. |
| | | |
| ## Sender requirements updates | | ## Sender requirements updates |
| | | |
| This table lists our updates to the sender guidelines and require | | This table lists our updates to the sender guidelines and require |
| ments: | | ments: |
| | | |
| Sender requirement | Date added | | Sender requirement | Date added |
| ---|--- | | ---|--- |
| Use a TLS connection for transmitting email | Dec. 2023 | | Use a TLS connection for transmitting email | Dec. 2023 |
| | | |
| ## Sender requirements and guidelines | | ## Sender requirements and guidelines |
| | | |
| Follow these guidelines to help ensure messages are delivered to | | Follow these guidelines to help ensure messages are delivered to |
| Gmail | | Gmail |
| accounts as expected, and to help prevent Gmail from limiting sen | | accounts as expected, and to help prevent Gmail from limiting sen |
| ding rates, | | ding rates, |
| blocking messages, or marking messages as spam. | | blocking messages, or marking messages as spam. |
| | | |
| Requirements for all senders | | Requirements for all senders |
| | | |
| Starting February 1, 2024, all email senders who send email to Gm | | Starting February 1, 2024, all email senders who send email to Gm |
| ail accounts | | ail accounts |
| must meet the requirements in this section. | | must meet the requirements in this section. |
| | | |
| **Important:** If you send more than 5,000 messages per day to Gm | | **Important:** If you send more than 5,000 messages per day to Gm |
| ail accounts, | | ail accounts, |
| follow the Requirements for sending 5,000 or more messages per da | | follow the Requirements for sending 5,000 or more messages per da |
| y. | | y. |
| | | |
| * Set up SPF or DKIM email authentication for your sending doma | | * Set up SPF or DKIM email authentication for your sending doma |
| ins. | | ins. |
| * Ensure that sending domains or IPs have valid forward and rev | | * Ensure that sending domains or IPs have valid forward and rev |
| erse DNS records, also referred to as PTR records. Learn more | | erse DNS records, also referred to as PTR records. Learn more |
| * Use a TLS connection for transmitting email. For steps to set | | * Use a TLS connection for transmitting email. For steps to set |
| up TLS in Google Workspace, visit Require a secure connection fo | | up TLS in Google Workspace, visit Require a secure connection fo |
| r email. | | r email. |
| * Keep spam rates reported in Postmaster Tools below 0.3%. Lear | | * Keep spam rates reported in Postmaster Tools below 0.3%. Lear |
| n more about spam rates | | n more about spam rates |
| * Format messages according to the Internet Message Format stan | | * Format messages according to the Internet Message Format stan |
| dard, RFC 5322. | | dard, RFC 5322. |
| n | * Don’t impersonate Gmail From: headers. Gmail will begin using | n | * Don’t impersonate Gmail From: headers. Gmail will begin using |
| a DMARC **quarantine** enforcement policy, and impersonating Gm | | a DMARC quarantine enforcement policy, and impersonating Gmail F |
| ail From: headers might impact your email delivery. | | rom: headers might impact your email delivery. |
| * If you manage a forwarding service, including mailing lists o | | * If you manage a forwarding service, including mailing lists o |
| r inbound gateways, add ARC headers to outgoing email. ARC header | | r inbound gateways, add ARC headers to outgoing email. ARC header |
| s indicate the message was forwarded and identify you as the forw | | s indicate the message was forwarded and identify you as the forw |
| arder. Mailing list senders should also add a List-id: header, wh | | arder. Mailing list senders should also add a List-id: header, wh |
| ich specifies the mailing list, to outgoing messages. | | ich specifies the mailing list, to outgoing messages. |
| | | |
| Requirements for sending 5,000 or more messages per day | | Requirements for sending 5,000 or more messages per day |
| | | |
| Starting February 1, 2024, email senders who send more than 5,000 | | Starting February 1, 2024, email senders who send more than 5,000 |
| messages per | | messages per |
| day to Gmail accounts must meet the requirements in this section. | | day to Gmail accounts must meet the requirements in this section. |
| | | |
| * Set up SPF and DKIM email authentication for your domain. | | * Set up SPF and DKIM email authentication for your domain. |
| n | | n | * Set up DMARC email authentication for your sending domain. Yo |
| | | ur DMARC enforcement policy can be set to none. Learn more |
| * Ensure that sending domains or IPs have valid forward and rev | | * Ensure that sending domains or IPs have valid forward and rev |
| erse DNS records, also referred to as PTR records. Learn more | | erse DNS records, also referred to as PTR records. Learn more |
| * Use a TLS connection for transmitting email. For steps to set | | * Use a TLS connection for transmitting email. For steps to set |
| up TLS in Google Workspace, visit Require a secure connection fo | | up TLS in Google Workspace, visit Require a secure connection fo |
| r email. | | r email. |
| * Keep spam rates reported in Postmaster Tools below 0.30%. Lea | | * Keep spam rates reported in Postmaster Tools below 0.30%. Lea |
| rn more about spam rates | | rn more about spam rates |
| * Format messages according to the Internet Message Format stan | | * Format messages according to the Internet Message Format stan |
| dard, RFC 5322. | | dard, RFC 5322. |
| n | * Don’t impersonate Gmail From: headers. Gmail will begin using | n | * Don’t impersonate Gmail From: headers. Gmail will begin using |
| a DMARC **quarantine** enforcement policy, and impersonating Gma | | a DMARC quarantine enforcement policy, and impersonating Gmail F |
| il From: headers might impact your email delivery. | | rom: headers might impact your email delivery. |
| * If you manage a forwarding service, including mailing lists o | | * If you manage a forwarding service, including mailing lists o |
| r inbound gateways, add ARC headers to outgoing email. ARC header | | r inbound gateways, add ARC headers to outgoing email. ARC header |
| s indicate the message was forwarded and identify you as the forw | | s indicate the message was forwarded and identify you as the forw |
| arder. Mailing list senders should also add a List-id: header, wh | | arder. Mailing list senders should also add a List-id: header, wh |
| ich specifies the mailing list, to outgoing messages. | | ich specifies the mailing list, to outgoing messages. |
| n | * Set up DMARC email authentication for your sending domain. Yo | n | |
| ur DMARC enforcement policy can be set to **none**. Learn more | | |
| * For direct mail, the domain in the sender's From: header must | | * For direct mail, the domain in the sender's From: header must |
| be aligned with either the SPF domain or the DKIM domain. This i | | be aligned with either the SPF domain or the DKIM domain. This i |
| s required to pass DMARC alignment. | | s required to pass DMARC alignment. |
| * Marketing messages and subscribed messages must support one-c | | * Marketing messages and subscribed messages must support one-c |
| lick unsubscribe, and include a clearly visible unsubscribe link | | lick unsubscribe, and include a clearly visible unsubscribe link |
| in the message body. Learn more | | in the message body. Learn more |
| | | |
| If you send more than 5,000 emails per day before February 1, 202 | | If you send more than 5,000 emails per day before February 1, 202 |
| 4, follow the | | 4, follow the |
| guidelines in this article as soon as possible. Meeting the sende | | guidelines in this article as soon as possible. Meeting the sende |
| r | | r |
| requirements before the deadline may improve your email delivery. | | requirements before the deadline may improve your email delivery. |
| If you don’t | | If you don’t |
| meet the requirements described in this article, your email might | | meet the requirements described in this article, your email might |
| not be | | not be |
| delivered as expected, or might be marked as spam. To get help wi | | delivered as expected, or might be marked as spam. To get help wi |
| th email | | th email |
| delivery issues, go to Troubleshooting. | | delivery issues, go to Troubleshooting. |
| | | |
| n | ### Email authentication requirements & recommendations | n | ### Email authentication requirements & guidelines |
| | | |
| n | We require that you set up these email authentication methods for | n | We require that you set up these email authentication methods for |
| your domain. | | your domain: |
| | | |
| | | * All senders: SPF or DKIM |
| | | * Bulk senders: SPF, DKIM, and DMARC |
| | | |
| Authenticated messages: | | Authenticated messages: |
| | | |
| * Help protect recipients from malicious messages, such as spoo | | * Help protect recipients from malicious messages, such as spoo |
| fing and phishing messages. | | fing and phishing messages. |
| * Help protect you and your organization from being impersonate | | * Help protect you and your organization from being impersonate |
| d. | | d. |
| * Are less likely to be rejected or marked as spam by Gmail. | | * Are less likely to be rejected or marked as spam by Gmail. |
| | | |
| Set up email authentication for each of your sending domains at y | | Set up email authentication for each of your sending domains at y |
| our domain | | our domain |
| provider. You can use instructions Google provides and our domain | | provider. You can use instructions Google provides and our domain |
| provider's | | provider's |
| email authentication support information. | | email authentication support information. |
| | | |
| To verify messages are authenticated, Google performs checks on m | | To verify messages are authenticated, Google performs checks on m |
| essages sent | | essages sent |
| to Gmail accounts. To improve email delivery, we recommend that y | | to Gmail accounts. To improve email delivery, we recommend that y |
| ou always set | | ou always set |
| up SPF, DKIM, and DMARC for your domains. Make sure you're meetin | | up SPF, DKIM, and DMARC for your domains. Make sure you're meetin |
| g the minimum | | g the minimum |
| authentication requirements described on this page. Messages that | | authentication requirements described on this page. Messages that |
| aren’t | | aren’t |
| authenticated with these methods might be marked as spam or rejec | | authenticated with these methods might be marked as spam or rejec |
| ted with a | | ted with a |
| n | **5.7.26** error. | n | 5.7.26 error. |
| | | |
| If you use an email service provider, verify that they authentica | | If you use an email service provider, verify that they authentica |
| te your | | te your |
| domain’s email with SPF and DKIM. | | domain’s email with SPF and DKIM. |
| | | |
| If you regularly forward email or manage a forwarding service, he | | If you regularly forward email or manage a forwarding service, he |
| lp ensure | | lp ensure |
| forwarded messages are authenticated by following our Best practi | | forwarded messages are authenticated by following our Best practi |
| ces for | | ces for |
| forwarding email to Gmail. | | forwarding email to Gmail. |
| | | |
| We recommend you always set up email authentication for the domai | | We recommend you always set up email authentication for the domai |
| n that hosts | | n that hosts |
| your public website | | your public website |
| | | |
| #### SPF | | #### SPF |
| | | |
| SPF prevents spammers from sending unauthorized messages that app | | SPF prevents spammers from sending unauthorized messages that app |
| ear to be | | ear to be |
| from your domain. Set up SPF by publishing an SPF record at your | | from your domain. Set up SPF by publishing an SPF record at your |
| domain. The | | domain. The |
| SPF record for your domain should include all email senders for y | | SPF record for your domain should include all email senders for y |
| our domain. | | our domain. |
| If your third-party senders aren't included in your SPF record, m | | If your third-party senders aren't included in your SPF record, m |
| essages from | | essages from |
| these senders are more likely to be marked as spam. Learn how to | | these senders are more likely to be marked as spam. Learn how to |
| define your | | define your |
| SPF record and add it to your domain. | | SPF record and add it to your domain. |
| | | |
| #### DKIM | | #### DKIM |
| | | |
| Turn on DKIM for the domain that sends your email. Receiving serv | | Turn on DKIM for the domain that sends your email. Receiving serv |
| ers use DKIM | | ers use DKIM |
| to verify that the domain owner actually sent the message. If you | | to verify that the domain owner actually sent the message. If you |
| use Google | | use Google |
| Workspace to send email, learn how to turn on DKIM for your domai | | Workspace to send email, learn how to turn on DKIM for your domai |
| n. If you | | n. If you |
| don’t use Google Workspace to send email, you can use one of many | | don’t use Google Workspace to send email, you can use one of many |
| available | | available |
| internet tools to create your DKIM keys, or check with your domai | | internet tools to create your DKIM keys, or check with your domai |
| n provider | | n provider |
| for help. | | for help. |
| | | |
| **Important:** Sending to personal Gmail accounts requires a DKIM | | **Important:** Sending to personal Gmail accounts requires a DKIM |
| key of 1024 | | key of 1024 |
| bits or longer. For security reasons, we recommend using a 2048-b | | bits or longer. For security reasons, we recommend using a 2048-b |
| it key if | | it key if |
| your domain provider supports this. Learn more about DKIM key len | | your domain provider supports this. Learn more about DKIM key len |
| gth. | | gth. |
| | | |
| #### DMARC | | #### DMARC |
| | | |
| DMARC tells receiving servers what to do with your messages that | | DMARC tells receiving servers what to do with your messages that |
| don’t pass | | don’t pass |
| SPF or DKIM. Set up DMARC by publishing a DMARC record for your d | | SPF or DKIM. Set up DMARC by publishing a DMARC record for your d |
| omain. To | | omain. To |
| pass DMARC authentication, messages must be authenticated by SPF | | pass DMARC authentication, messages must be authenticated by SPF |
| or DKIM, or | | or DKIM, or |
| both. The authenticating domain must be the same domain that appe | | both. The authenticating domain must be the same domain that appe |
| ars in the | | ars in the |
| message From: header. Learn how to add a DMARC record at your dom | | message From: header. Learn how to add a DMARC record at your dom |
| ain. | | ain. |
| | | |
| We recommend you set up DMARC reports so you can monitor email se | | We recommend you set up DMARC reports so you can monitor email se |
| nt from your | | nt from your |
| domain, or appears to have been sent from your domain. DMARC repo | | domain, or appears to have been sent from your domain. DMARC repo |
| rts help you | | rts help you |
| identify senders that may be impersonating your domain. Learn mor | | identify senders that may be impersonating your domain. Learn mor |
| e about DMARC | | e about DMARC |
| reports. | | reports. |
| | | |
| #### ARC | | #### ARC |
| | | |
| ARC checks the previous authentication status of forwarded messag | | ARC checks the previous authentication status of forwarded messag |
| es. If a | | es. If a |
| forwarded message passes SPF or DKIM authentication, but ARC show | | forwarded message passes SPF or DKIM authentication, but ARC show |
| s it | | s it |
| previously failed authentication, Gmail treats the message as una | | previously failed authentication, Gmail treats the message as una |
| uthenticated. | | uthenticated. |
| | | |
| We recommend that senders use ARC authentication, especially if t | | We recommend that senders use ARC authentication, especially if t |
| hey regularly | | hey regularly |
| forward email. Learn more about ARC authentication. | | forward email. Learn more about ARC authentication. |
| | | |
| n | ### Infrastructure configuration | n | ### Infrastructure configuration requirements and guidelines |
| | | |
| #### IP addresses | | #### IP addresses |
| | | |
| **Important:** The sending IP address must match the IP address o | | **Important:** The sending IP address must match the IP address o |
| f the | | f the |
| hostname specified in the Pointer (PTR) record. | | hostname specified in the Pointer (PTR) record. |
| | | |
| The public IP address of a sending SMTP server must have a corres | | The public IP address of a sending SMTP server must have a corres |
| ponding PTR | | ponding PTR |
| record that resolves to a hostname. This is called a _reverse DNS | | record that resolves to a hostname. This is called a _reverse DNS |
| lookup_. The | | lookup_. The |
| same hostname must also have an A (for IPv4) or AAAA (for IPv6) r | | same hostname must also have an A (for IPv4) or AAAA (for IPv6) r |
| ecord that | | ecord that |
| resolves to the same public IP address used by the sending server | | resolves to the same public IP address used by the sending server |
| . This is | | . This is |
| called a _forward DNS lookup_. | | called a _forward DNS lookup_. |
| | | |
| Set up valid reverse DNS records of your sending server IP addres | | Set up valid reverse DNS records of your sending server IP addres |
| ses that | | ses that |
| point to your domain. Check for a PTR record with the Google Admi | | point to your domain. Check for a PTR record with the Google Admi |
| n Toolbox Dig | | n Toolbox Dig |
| tool. | | tool. |
| | | |
| **Important:** The sending IP address must match the IP address o | | **Important:** The sending IP address must match the IP address o |
| f the | | f the |
| hostname specified in the Pointer (PTR) record. | | hostname specified in the Pointer (PTR) record. |
| | | |
| #### Shared IP addresses | | #### Shared IP addresses |
| | | |
| A shared IP address is an IP address used by more than one email | | A shared IP address is an IP address used by more than one email |
| sender. The | | sender. The |
| activity of any senders using a shared IP address affects the rep | | activity of any senders using a shared IP address affects the rep |
| utation of | | utation of |
| all senders for that shared IP address. A negative reputation can | | all senders for that shared IP address. A negative reputation can |
| impact your | | impact your |
| delivery rate. | | delivery rate. |
| | | |
| If you use a shared IP address for sending email: | | If you use a shared IP address for sending email: |
| | | |
| * Make sure the shared IP address isn’t on any internet blockli | | * Make sure the shared IP address isn’t on any internet blockli |
| st. Messages sent from IP addresses on a blocklist are more likel | | st. Messages sent from IP addresses on a blocklist are more likel |
| y to be marked as spam. | | y to be marked as spam. |
| * If you use an email service provider for your shared IP, use | | * If you use an email service provider for your shared IP, use |
| Postmaster Tools to check the reputation of the shared IP addres | | Postmaster Tools to check the reputation of the shared IP addres |
| s. | | s. |
| | | |
| n | ### Subscriptions | n | ### Subscription requirements and guidelines |
| | | |
| n | | n | If you manage mailing lists or other email subscriptions, you sho |
| | | uld send |
| Send email only to people who want to get messages from you. Thes | | email only to people who want to get messages from you. These rec |
| e recipients | | ipients are |
| are less likely to report your messages as spam. | | less likely to report your messages as spam. If messages from you |
| | | r domain are |
| | | frequently reported as spam, future messages from you are more li |
| | | kely to be |
| If messages from your domain are frequently reported as spam, fut | | marked as spam. Over time, user spam reports can lower your domai |
| ure messages | | n’s |
| from you are more likely to be marked as spam. Over time, user sp | | reputation. Check your spam rate and your reputation with Postmas |
| am reports | | ter Tools. |
| can lower your domain’s reputation. Check your domain’s reputatio | | |
| n with | | |
| Postmaster Tools. | | |
| | | |
| #### Make it easy to subscribe | | #### Make it easy to subscribe |
| | | |
| n | To help ensure your recipients are engaged: | n | To help ensure recipients are engaged: |
| | | |
| * Make sure recipients opt in to get messages from you. | | * Make sure recipients opt in to get messages from you. |
| * Confirm each recipient's email address before subscribing the | | * Confirm each recipient's email address before subscribing the |
| m. | | m. |
| * Periodically send messages to confirm that recipients want to | | * Periodically send messages to confirm that recipients want to |
| stay subscribed. | | stay subscribed. |
| * Consider unsubscribing recipients who don’t open or read your | | * Consider unsubscribing recipients who don’t open or read your |
| messages. | | messages. |
| | | |
| #### Make it easy to unsubscribe | | #### Make it easy to unsubscribe |
| | | |
| Always give recipients an easy way to unsubscribe from your messa | | Always give recipients an easy way to unsubscribe from your messa |
| ges. Letting | | ges. Letting |
| people opt out of your messages can improve open rates, click-thr | | people opt out of your messages can improve open rates, click-thr |
| ough rates, | | ough rates, |
| and sending efficiency. | | and sending efficiency. |
| | | |
| **Important:** If you send more than 5,000 message per day, your | | **Important:** If you send more than 5,000 message per day, your |
| marketing and | | marketing and |
| subscribed messages must support one-click unsubscribe. | | subscribed messages must support one-click unsubscribe. |
| | | |
| To set up one-click unsubscribe for Gmail messages, include both | | To set up one-click unsubscribe for Gmail messages, include both |
| of these | | of these |
| headers in outgoing messages: | | headers in outgoing messages: |
| | | |
| n | * List-Unsubscribe-Post: `List-Unsubscribe=One-Click` | n | * List-Unsubscribe-Post: List-Unsubscribe=One-Click |
| | | |
| * List-Unsubscribe: `<https://solarmora.com/unsubscribe/example | | * List-Unsubscribe: <https://solarmora.com/unsubscribe/example> |
| >` | | |
| | | |
| When a recipient unsubscribes using one-click, you receive this P | | When a recipient unsubscribes using one-click, you receive this P |
| OST request: | | OST request: |
| | | |
| n | `"POST /unsubscribe/example HTTP/1.1 | n | "POST /unsubscribe/example HTTP/1.1 |
| Host: solarmora.com | | Host: solarmora.com |
| Content-Type: application/x-www-form-urlencoded | | Content-Type: application/x-www-form-urlencoded |
| Content-Length: 26 | | Content-Length: 26 |
| n | List-Unsubscribe=One-Click"` | n | List-Unsubscribe=One-Click" |
| | | |
| Learn more about List-Unsubscribe: headers in RFC 2369 and RFC 80 | | Learn more about List-Unsubscribe: headers in RFC 2369 and RFC 80 |
| 58. | | 58. |
| | | |
| These unsubscribe options can also be used but they should not re | | These unsubscribe options can also be used but they should not re |
| place one- | | place one- |
| click unsubscribe: | | click unsubscribe: |
| | | |
| * Let recipients review the individual mailing lists they’re su | | * Let recipients review the individual mailing lists they’re su |
| bscribed to. Let them unsubscribe from lists individually, or all | | bscribed to. Let them unsubscribe from lists individually, or all |
| lists at once. | | lists at once. |
| * Automatically unsubscribe recipients who have multiple bounce | | * Automatically unsubscribe recipients who have multiple bounce |
| d messages. | | d messages. |
| | | |
| n | ### Message formatting | n | ### Message formatting requirements and guidelines |
| | | |
| n | Follow these message formatting guidelines to increase the likeli | n | Follow these message formatting guidelines to help ensure message |
| hood that | | s are |
| Gmail delivers your messages to the inbox instead of the spam fol | | delivered as expected: |
| der: | | |
| | | |
| n | * Format messages according to the Internet Format Standard (RF | n | |
| C 5322). | | |
| * If your messages are in HTML, format them according to HTML s | | * If your messages are in HTML, format them according to HTML s |
| tandards. | | tandards. |
| n | | n | * Follow these message header guidelines: |
| | | * From: headers should include only one email address. For ex |
| | | ample: |
| | | From: notifications@solarmora.com |
| | | |
| | | * Avoid excessively large message headers. To learn more, vis |
| | | it Gmail message header limits. |
| | | * Format messages according to the Internet Format Standard (RF |
| | | C 5322). |
| | | * Make sure every message includes a valid Message-ID. |
| | | * Make sure single-instance message headers are included only |
| | | once in a message. Examples of single-instance headers include F |
| | | rom:, To:, Subject:, and Date:. |
| | | * Message headers and message content should be accurate, and n |
| | | ot misleading or deceptive. |
| | | * Email message subject, headers, display names, and other me |
| | | ssage elements should accurately represent the sender identity an |
| | | d message content, and shouldn’t be misleading. For example, don’ |
| | | t send messages with subject lines starting with Re: or Fwd: unle |
| | | ss the messages are actual replies or forwards, and include only |
| | | actual senders and recipients in From: and To: headers. |
| | | * Don't use emojis or other non-standard characters to imitat |
| | | e graphic elements in messages, with the intent to deceive or inf |
| | | luence recipients. For example, don’t use emojis or images next t |
| | | o display or brand names to imply the name has been verified in s |
| | | ome way. |
| * Don’t use HTML and CSS to hide content in your messages. Hidi | | * Don’t use HTML and CSS to hide content in your messages. Hi |
| ng content might cause messages to be marked as spam. | | ding content might cause messages to be marked as spam. |
| * Message From: headers should include only one email address. | | |
| For example: | | |
| `From: notifications@solarmora.com` | | |
| | | |
| * Make sure every message includes a valid Message-ID (RFC 5322 | | |
| ). | | |
| * Make sure single-instance message headers are included only o | | |
| nce in a message. Examples of single-instance headers include Fro | | |
| m, To, Subject, and Date (RFC 5322). | | |
| * Avoid excessively large message headers. To learn more, visit | | |
| Gmail message header limits. | | |
| * Web links in the message body should be visible and easy to u | | * Web links in the message body should be visible and easy to |
| nderstand. Recipients should know what to expect when they click | | understand. Recipients should know what to expect when they clic |
| a link. | | k a link. |
| * Sender information should be clear and visible. | | * Sender information should be clear and visible. |
| * Message subjects should be accurate and not misleading. | | * * Format the following international domains according to S |
| | | ection 5.2 of Unicode Technical Standard #39. An international do |
| | | main is also called an _internationalized domain name (IDN_ ), a |
| | | nd is a URL that is specific to a region or country. |
| * Format these international domains according to the Highly Re | | |
| strictive guidelines in section 5.2 of Unicode Technical Standard | | |
| #39: | | |
| * Authenticating domain | | * Authenticating domain |
| * Envelope from domain | | * Envelope from domain |
| * Payload domain | | * Payload domain |
| * Reply-to domain | | * Reply-to domain |
| * Sender domain | | * Sender domain |
| | | |
| n | ## Sending guidelines | n | ### Sending practices requirements and guidelines |
| | | |
| To reduce the chances that messages from your domain are sent to | | To reduce the chances that messages from your domain are sent to |
| spam or | | spam or |
| blocked by Gmail, follow the best practices in this section. | | blocked by Gmail, follow the best practices in this section. |
| | | |
| * Authenticate email with SPF and DKIM that are aligned with ea | | * Authenticate email with SPF and DKIM that are aligned with ea |
| ch other at the organizational level. If you use an email provide | | ch other at the organizational level. If you use an email provide |
| r, verify that your provider supports this. | | r, verify that your provider supports this. |
| * Ideally, send all messages from the same IP address. If you m | | * Ideally, send all messages from the same IP address. If you m |
| ust send from multiple IP addresses, use a different IP address f | | ust send from multiple IP addresses, use a different IP address f |
| or each message type. For example, use one IP address for sending | | or each message type. For example, use one IP address for sending |
| account notifications and a different IP address for sending pro | | account notifications and a different IP address for sending pro |
| motional messages. | | motional messages. |
| * Messages of the same category should have the same From: emai | | * Messages of the same category should have the same From: emai |
| l address. For example, messages from a domain called `solarmora. | | l address. For example, messages from a domain called `solarmora. |
| com` might have From: addresses like: | | com` might have From: addresses like: |
| * Sales receipt messages: `sales@solarmora.com` | | * Sales receipt messages: `sales@solarmora.com` |
| * Promotional messages: `deals@solarmora.com` | | * Promotional messages: `deals@solarmora.com` |
| * Account notification messages: `alert@solarmora.com` | | * Account notification messages: `alert@solarmora.com` |
| * Messages sent from an address in the recipient’s contacts are | | * Messages sent from an address in the recipient’s contacts are |
| less likely to be marked as spam. | | less likely to be marked as spam. |
| | | |
| #### Sending practices to avoid | | #### Sending practices to avoid |
| | | |
| * Don't mix different types of content in the same message. For | | * Don't mix different types of content in the same message. For |
| example, don't include promotions in sales receipt messages. | | example, don't include promotions in sales receipt messages. |
| * Don't impersonate other domains or senders without permission | | * Don't impersonate other domains or senders without permission |
| . This practice is called _spoofing_ , and Gmail might mark these | | . This practice is called _spoofing_ , and Gmail might mark these |
| messages as spam. | | messages as spam. |
| * Don't mark internal messages as spam. This can negatively aff | | * Don't mark internal messages as spam. This can negatively aff |
| ect your domain's reputation, and future messages might be marked | | ect your domain's reputation, and future messages might be marked |
| as spam. | | as spam. |
| * Don't purchase email addresses from other companies. | | * Don't purchase email addresses from other companies. |
| * Don't send messages to people who didn't sign up to get messa | | * Don't send messages to people who didn't sign up to get messa |
| ges from you. These recipients might mark your messages as spam, | | ges from you. These recipients might mark your messages as spam, |
| and future messages to these recipients will be marked as spam. | | and future messages to these recipients will be marked as spam. |
| * Avoid opt-in forms that are checked by default and that autom | | * Avoid opt-in forms that are checked by default and that autom |
| atically subscribe users. Some countries and regions restrict aut | | atically subscribe users. Some countries and regions restrict aut |
| omatic opt-in. Before you opt-in users automatically, check the r | | omatic opt-in. Before you opt-in users automatically, check the r |
| egulations in your region. | | egulations in your region. |
| | | |
| Some legitimate messages may be marked as spam. Recipients can ma | | Some legitimate messages may be marked as spam. Recipients can ma |
| rk valid | | rk valid |
| messages as not spam, so future messages from the sender should b | | messages as not spam, so future messages from the sender should b |
| e delivered | | e delivered |
| to their inbox. | | to their inbox. |
| | | |
| n | ### Increase sending volume slowly | n | #### Increase sending volume slowly |
| | | |
| When increasing sending volume, keep in mind: | | When increasing sending volume, keep in mind: |
| | | |
| * Increasing the sending volume too quickly can result in deliv | | * Increasing the sending volume too quickly can result in deliv |
| ery problems. As you gradually increase your sending mail volume, | | ery problems. As you gradually increase your sending mail volume, |
| use Postmaster Tools to monitor email delivery. | | use Postmaster Tools to monitor email delivery. |
| * For Google Workspace work and school accounts, sending limits | | * For Google Workspace work and school accounts, sending limits |
| apply even when recipients are in different Google Workspace dom | | apply even when recipients are in different Google Workspace dom |
| ains. For example, you might send email to users with email addre | | ains. For example, you might send email to users with email addre |
| sses that have the domains `your-company.net` and `solarmora.com` | | sses that have the domains `your-company.net` and `solarmora.com` |
| _. _Although the domains are different, if both domains have `g | | _. _Although the domains are different, if both domains have `g |
| oogle.com` as their MX record, messages sent to these domains cou | | oogle.com` as their MX record, messages sent to these domains cou |
| nt toward your limit. | | nt toward your limit. |
| * If you use Google Workspace or Gmail for sending: When you re | | * If you use Google Workspace or Gmail for sending: When you re |
| ach the sending limit, the sending rate is limited for the sendin | | ach the sending limit, the sending rate is limited for the sendin |
| g IP address. | | g IP address. |
| | | |
| If you send large amounts of email, we recommend you: | | If you send large amounts of email, we recommend you: |
| | | |
| * Send email at a consistent rate. Avoid sending email in burst | | * Send email at a consistent rate. Avoid sending email in burst |
| s. | | s. |
| * Start with a low sending volume to engaged users, and slowly | | * Start with a low sending volume to engaged users, and slowly |
| increase the volume over time. | | increase the volume over time. |
| * As you increase the sending volume, regularly monitor server | | * As you increase the sending volume, regularly monitor server |
| responses, spam rate, and the sending domain's reputation. Regula | | responses, spam rate, and the sending domain's reputation. Regula |
| r monitoring will allow you to quickly adapt if your sending is r | | r monitoring will allow you to quickly adapt if your sending is r |
| ate limited, if the spam rate is increased, or when the sending d | | ate limited, if the spam rate is increased, or when the sending d |
| omain's reputation drops. | | omain's reputation drops. |
| * Avoid introducing sudden volume spikes if you do not have a h | | * Avoid introducing sudden volume spikes if you do not have a h |
| istory of sending large volumes. For example, immediately doublin | | istory of sending large volumes. For example, immediately doublin |
| g previously sent volumes suddenly could result in rate limiting | | g previously sent volumes suddenly could result in rate limiting |
| or reputation drops. | | or reputation drops. |
| * If you change the format of your bulk emails, gradually incre | | * If you change the format of your bulk emails, gradually incre |
| ase the sending volume of messages with the new format. | | ase the sending volume of messages with the new format. |
| * After making any significant changes to your sending infrastr | | * After making any significant changes to your sending infrastr |
| ucture or email header structure, increase the modified segment o | | ucture or email header structure, increase the modified segment o |
| f traffic separately. | | f traffic separately. |
| * If messages start bouncing or start being deferred, reduce th | | * If messages start bouncing or start being deferred, reduce th |
| e sending volume until the SMTP error rate decreases. Then, incre | | e sending volume until the SMTP error rate decreases. Then, incre |
| ase slowly again. If bounces and deferrals continue at a low volu | | ase slowly again. If bounces and deferrals continue at a low volu |
| me, review individual messages to identify problems. For example, | | me, review individual messages to identify problems. For example, |
| you can try sending a blank test message and see if it experienc | | you can try sending a blank test message and see if it experienc |
| es issues. | | es issues. |
| * Stay within the IP limits for sending: | | * Stay within the IP limits for sending: |
| * Be aware of email sending limits when sending from domains | | * Be aware of email sending limits when sending from domains |
| that have a Google.com MX host. | | that have a Google.com MX host. |
| * Limit sending email from a single IP address based on the M | | * Limit sending email from a single IP address based on the M |
| X record domain, not the domain in the recipient email address. | | X record domain, not the domain in the recipient email address. |
| * Monitor responses so you can change sending rates as needed | | * Monitor responses so you can change sending rates as needed |
| to stay within these limits. | | to stay within these limits. |
| | | |
| These factors affect how quickly you can increase sending volume: | | These factors affect how quickly you can increase sending volume: |
| | | |
| * Amount of email sent: The more email that you send, the more | | * Amount of email sent: The more email that you send, the more |
| slowly you should increase sending volume. | | slowly you should increase sending volume. |
| * Frequency of sending email: You can increase the sending volu | | * Frequency of sending email: You can increase the sending volu |
| me more quickly when you send daily instead of weekly. | | me more quickly when you send daily instead of weekly. |
| * Recipient feedback about your messages: Make sure you send on | | * Recipient feedback about your messages: Make sure you send on |
| ly to people who subscribe to your emails, and give recipients an | | ly to people who subscribe to your emails, and give recipients an |
| option to unsubscribe. | | option to unsubscribe. |
| | | |
| In the event of a recent spike in email activity, we recommend fo | | In the event of a recent spike in email activity, we recommend fo |
| llowing the | | llowing the |
| requirements and guidelines on this page to resolve deliverabilit | | requirements and guidelines on this page to resolve deliverabilit |
| y issues | | y issues |
| automatically during following sends. | | automatically during following sends. |
| | | |
| n | ## Special considerations | n | ## Additional guidelines |
| | | |
| n | ### If you use an email service provider | n | ### Guidelines for using email service providers |
| | | |
| Google and Gmail don’t accept allowlist requests from email provi | | Google and Gmail don’t accept allowlist requests from email provi |
| ders. We | | ders. We |
| can't guarantee messages sent by email providers will pass Gmail’ | | can't guarantee messages sent by email providers will pass Gmail’ |
| s spam | | s spam |
| filters. | | filters. |
| | | |
| If you use a third-party email provider to send email for your do | | If you use a third-party email provider to send email for your do |
| main: | | main: |
| | | |
| * Verify that the provider follows the guidelines on this page. | | * Verify that the provider follows the guidelines on this page. |
| Large providers, such as Google, AOL, and Yahoo, typically follo | | Large providers, such as Google, AOL, and Yahoo, typically follo |
| w these guidelines. | | w these guidelines. |
| * Make sure the SPF record for your domain includes all email s | | * Make sure the SPF record for your domain includes all email s |
| enders for your domain. If third-party senders aren't included in | | enders for your domain. If third-party senders aren't included in |
| your SPF record, messages sent from these providers are more lik | | your SPF record, messages sent from these providers are more lik |
| ely to be marked as spam. Learn how to set up your SPF record. | | ely to be marked as spam. Learn how to set up your SPF record. |
| | | |
| If you use a domain provider but you manage your own email, we re | | If you use a domain provider but you manage your own email, we re |
| commend you: | | commend you: |
| | | |
| * Review and follow the requirements and guidelines on this pag | | * Review and follow the requirements and guidelines on this pag |
| e. | | e. |
| * Use Postmaster Tools to monitor information about messages se | | * Use Postmaster Tools to monitor information about messages se |
| nt from your domain to Gmail accounts. | | nt from your domain to Gmail accounts. |
| | | |
| n | ### If you are a third-party email provider | n | ### Guidelines for email service providers |
| | | |
| When clients use your service to send email, you’re responsible f | | When clients use your service to send email, you’re responsible f |
| or their | | or their |
| sending practices. We recommend taking these steps to help manage | | sending practices. We recommend taking these steps to help manage |
| your | | your |
| clients’ sending activity: | | clients’ sending activity: |
| | | |
| * Offer an email address for reporting email abuse, for example | | * Offer an email address for reporting email abuse, for example |
| : `abuse@mail-provider.com`. | | : `abuse@mail-provider.com`. |
| * Make sure your contact information in your WHOIS record and o | | * Make sure your contact information in your WHOIS record and o |
| n abuse.net is current. | | n abuse.net is current. |
| * Immediately remove any client who uses your service to send s | | * Immediately remove any client who uses your service to send s |
| pam. | | pam. |
| | | |
| ### Affiliate marketing | | ### Affiliate marketing |
| | | |
| Affiliate marketing programs offer rewards to companies or indivi | | Affiliate marketing programs offer rewards to companies or indivi |
| duals that | | duals that |
| send visitors to your website. However, spammers can abuse these | | send visitors to your website. However, spammers can abuse these |
| programs. If | | programs. If |
| your brand is associated with marketing spam, other messages sent | | your brand is associated with marketing spam, other messages sent |
| by you might | | by you might |
| be marked as spam. | | be marked as spam. |
| | | |
| We recommend you regularly monitor affiliates, and remove any aff | | We recommend you regularly monitor affiliates, and remove any aff |
| iliates that | | iliates that |
| send spam. | | send spam. |
| | | |
| ### Phishing exercises | | ### Phishing exercises |
| | | |
| Don’t send test phishing messages or test campaigns from your dom | | Don’t send test phishing messages or test campaigns from your dom |
| ain. Your | | ain. Your |
| domain’s reputation might be negatively affected, and your domain | | domain’s reputation might be negatively affected, and your domain |
| could be | | could be |
| added to internet blocklists. | | added to internet blocklists. |
| | | |
| ## Monitoring and troubleshooting | | ## Monitoring and troubleshooting |
| | | |
| ### Postmaster Tools | | ### Postmaster Tools |
| | | |
| Use Postmaster Tools to get information about the email you send | | Use Postmaster Tools to get information about the email you send |
| to Gmail | | to Gmail |
| users, for example: | | users, for example: |
| | | |
| * When recipients mark your messages as spam | | * When recipients mark your messages as spam |
| n | * Why your messages might not be delivered | n | * Why messages might not be delivered as expected |
| * If your messages are authenticated | | * If messages are authenticated |
| * Your domain or IP reputation and its impact on message delive | | * Your domain or IP reputation and the impact on message delive |
| ry rates | | ry rates |
| | | |
| #### Spam rate | | #### Spam rate |
| | | |
| * #### Regularly monitor your domain's spam rate in Postmaster | | * #### Regularly monitor your domain's spam rate in Postmaster |
| Tools. | | Tools. |
| | | |
| * Keep spam rates reported in Postmaster Tools below 0.10% and | | * Keep spam rates reported in Postmaster Tools below 0.10% and |
| avoid ever reaching a spam rate of 0.30% or higher. Learn more | | avoid ever reaching a spam rate of 0.30% or higher. Learn more |
| * Maintaining a low spam rate helps senders be more resilient t | | * Maintaining a low spam rate helps senders be more resilient t |
| o occasional spikes in user feedback. | | o occasional spikes in user feedback. |
| * Maintaining a high spam rate leads to increased spam classifi | | * Maintaining a high spam rate leads to increased spam classifi |
| cation. It can take time for improvements in spam rate to reflect | | cation. It can take time for improvements in spam rate to reflect |
| positively on spam classification. | | positively on spam classification. |
| | | |
| #### Open rate | | #### Open rate |
| | | |
| n | * Google does not explicitly track open rates. | n | * Google doesn't track open rates. |
| * Google isn’t able to verify the accuracy of open rates report | | * Google can't verify the accuracy of open rates reported by th |
| ed by third parties. | | ird parties. |
| * Low open rates may not be an accurate indicator of deliverabi | | * Low open rates aren't necessarily an accurate indicator of de |
| lity or spam classification issues. | | liverability or spam classification issues. |
| | | |
| n | ### Troubleshooting | n | ### Troubleshooting email delivery |
| | | |
| n | #### Warning banners | n | If messages aren't being delivered as expected: |
| | | |
| * Check regularly that your domain isn’t listed as unsafe with | | * Check regularly that your domain isn’t listed as unsafe with |
| Google Safe Browsing. | | Google Safe Browsing. |
| * To check your domain status, enter your domain in the Safe Br | | * To check your domain status, enter your domain in the Safe Br |
| owsing site status page. | | owsing site status page. |
| * Regularly check the status of any domains that are linked to | | * Regularly check the status of any domains that are linked to |
| yours. | | yours. |
| | | |
| n | #### Delivery issues when sending through email service providers | n | #### Sending with email service providers |
| | | |
| If you’re having delivery issues with email sent by a service pro | | If you’re having delivery issues with email sent by a service pro |
| vider, verify | | vider, verify |
| n | that they use the recommended practices in this article. | n | the provider follows the requirements and guidelines on this page |
| | | . |
| | | |
| #### Use the Google Admin Toolbox to review domain settings | | #### Use the Google Admin Toolbox to review domain settings |
| | | |
| Use the Google Admin Toolbox to check and fix settings for your d | | Use the Google Admin Toolbox to check and fix settings for your d |
| omain. | | omain. |
| | | |
| #### Fix the source of rejected email | | #### Fix the source of rejected email |
| | | |
| If your messages are rejected, you might get an error message. Le | | If your messages are rejected, you might get an error message. Le |
| arn more | | arn more |
| about the error so you can fix the problem. Common error messages | | about the error so you can fix the problem. Common error messages |
| are: | | are: |
| | | |
| * **421, "4.7.0":** **** Messages are rejected because the send | | * **421, "4.7.0":** **** Messages are rejected because the send |
| ing server’s IP address is not on the allowed list for the recipi | | ing server’s IP address is not on the allowed list for the recipi |
| ent’s domain. | | ent’s domain. |
| * **550, "5.7.1":** Messages are rejected because the sending s | | * **550, "5.7.1":** Messages are rejected because the sending s |
| erver’s IP address is on an IP suspended list. You might get this | | erver’s IP address is on an IP suspended list. You might get this |
| error if you’re sending mail using a shared IP with a poor reput | | error if you’re sending mail using a shared IP with a poor reput |
| ation. | | ation. |
| | | |
| Learn more about email and SMTP error messages: | | Learn more about email and SMTP error messages: |
| | | |
| * SMTP error reference | | * SMTP error reference |
| * Fix bounced or rejected emails | | * Fix bounced or rejected emails |
| | | |
| #### Fix IPv6 authorization errors | | #### Fix IPv6 authorization errors |
| | | |
| An IPv6 authorization error could mean that the PTR record for th | | An IPv6 authorization error could mean that the PTR record for th |
| e sending | | e sending |
| server isn’t using IPv6. If you use an email service provider, co | | server isn’t using IPv6. If you use an email service provider, co |
| nfirm they’re | | nfirm they’re |
| using an IPv6 PTR record. | | using an IPv6 PTR record. |
| | | |
| Here's an example of an IPv6 authorization error: | | Here's an example of an IPv6 authorization error: |
| | | |
| **550-5.7.1:** Message does not meet IPv6 sending guidelines rega | | **550-5.7.1:** Message does not meet IPv6 sending guidelines rega |
| rding PTR | | rding PTR |
| records and authentication. | | records and authentication. |
| | | |
| #### Use the troubleshooting tool | | #### Use the troubleshooting tool |
| | | |
| If you’re still having mail delivery problems after following the | | If you’re still having mail delivery problems after following the |
| guidelines | | guidelines |
| in this article, try Troubleshooting for senders with email deliv | | in this article, try Troubleshooting for senders with email deliv |
| ery issues. | | ery issues. |
| | | |
| n | Translations of our policies are provided for your convenience. I | n | |
| f there is a | | |
| conflict between the text of this policy and the text of the Engl | | |
| ish language | | |
| version of the policy, the text of the English language version o | | |
| f the policy | | |
| takes precedence. | | |
| | | |
| ## Related topics | | ## Related topics |
| | | |
| * Email sender guidelines FAQ | | * Email sender guidelines FAQ |
| * Fixed bounced emails | | * Fixed bounced emails |
| * Fix messages rejected by Google Groups | | * Fix messages rejected by Google Groups |
| | | |
| t | | t | _Translations of our policies are provided for your convenience. |
| | | If there is a |
| | | conflict between the text of this policy in language other than E |
| | | nglish and |
| | | the text of the English language version of the policy, the text |
| | | of the |
| | | English language version of the policy takes precedence._ |
| | | |
| ## Was this helpful? | | ## Was this helpful? |
| | | |
| How can we improve it? | | How can we improve it? |
| | | |
| YesNo | | YesNo |
| | | |
| Submit | | Submit |
| | | |
| ## Need more help? | | ## Need more help? |
| | | |
| ### Try these next steps: | | ### Try these next steps: |
| | | |
| Post to the help community Get answers from community members | | Post to the help community Get answers from community members |
| | | |
| Contact us Tell us more and we’ll help you get there | | Contact us Tell us more and we’ll help you get there |
| | | |
| true | | true |
| | | |
| ## Problems with sending | | ## Problems with sending |
| | | |
| * 1 of 10 | | * 1 of 10 |
| | | |
| Fix bounced or rejected emails | | Fix bounced or rejected emails |
| | | |
| * 2 of 10 | | * 2 of 10 |
| | | |
| Fix email bounces due to blocked IP address | | Fix email bounces due to blocked IP address |
| | | |
| * 3 of 10 | | * 3 of 10 |
| | | |
| Messages from a bulk sender bounce | | Messages from a bulk sender bounce |
| | | |
| * 4 of 10 | | * 4 of 10 |
| | | |
| Message bounced due to a policy rule | | Message bounced due to a policy rule |
| | | |
| * 5 of 10 | | * 5 of 10 |
| | | |
| Email bounces with error message | | Email bounces with error message |
| | | |
| * 6 of 10 | | * 6 of 10 |
| | | |
| Avoid email bouncing from new MX records | | Avoid email bouncing from new MX records |
| | | |
| * 7 of 10 | | * 7 of 10 |
| | | |
| Best practices for forwarding email to Gmail | | Best practices for forwarding email to Gmail |
| | | |
| * 8 of 10 | | * 8 of 10 |
| | | |
| Some recipients don't get my email | | Some recipients don't get my email |
| | | |
| * 9 of 10 | | * 9 of 10 |
| | | |
| SMTP relay spam policy in Gmail | | SMTP relay spam policy in Gmail |
| | | |
| * 10 of 10 | | * 10 of 10 |
| | | |
| Email sender guidelines | | Email sender guidelines |
| | | |
|  | | fL_3tU0Xvn4tJ3_POtw4haXNbIx7OL7v52_DcaBpe=w96) |
| | | |
| Start your free 14-day trial today | | Start your free 14-day trial today |
| | | |
| Professional email, online storage, shared calendars, video meeti | | Professional email, online storage, shared calendars, video meeti |
| ngs and more. | | ngs and more. |
| Start your free Google Workspace trial today. | | Start your free Google Workspace trial today. |
| | | |
| * ©2024 Google | | * ©2024 Google |
| * Privacy Policy | | * Privacy Policy |
| * Terms of Service | | * Terms of Service |
| | | |
| DeutschespañolfrançaisIndonesiaitalianoNederlandspolskiportuguês | | DeutschespañolfrançaisIndonesiaitalianoNederlandspolskiportuguês |
| (Brasil)svenskaTiếng | | (Brasil)svenskaTiếng |
| ViệtTürkçeрусскийукраїнськаעבריתالعربيةไทย中文（简体）中文（繁體）日本語한국어 Engl | | ViệtTürkçeрусскийукраїнськаעבריתالعربيةไทย中文（简体）中文（繁體）日本語한국어 Engl |
| ish | | ish |
| | | |
| Enable Dark Mode | | Enable Dark Mode |
| | | |
| Send feedback on... | | Send feedback on... |
| | | |
| This help content & information General Help Center experience | | This help content & information General Help Center experience |
| | | |
| Search | | Search |
| | | |
| Clear search | | Clear search |
| | | |
| Close search | | Close search |
| | | |
| Google apps | | Google apps |
| | | |
| Main menu | | Main menu |
| | | |
| | | |
| | | |
| true | | true |
| | | |
| Search Help Center | | Search Help Center |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| true | | true |
| | | |
| | | |
| | | |
| false | | false |
| | | |
| false | | false |
| | | |
| | | |