You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mozillafest.world domain is registered with Amazon Route 53 and it is scheduled to automatically renew on 2025-01-12. You have enabled automatic annual renewal for this domain.
You will be charged $13 USD for the renewal of the domain [1].
If you want to keep the domain, no further action is needed. On 2025-01-12, we'll charge an annual registration fee to your AWS account.
If you don't want us to renew registration for mozillafest.world, disable automatic renewal (instructions here) before 2025-01-12. If you disable automatic renewal, the domain will expire on 2025-02-16. You will receive two email reminders before expiration, as required by ICANN.
The registration price depends on the top-level domain (TLD). For more information, see AWS Route53 pricing.
Based on the following email:
Dear AWS customer,
The mozillafest.world domain is registered with Amazon Route 53 and it is scheduled to automatically renew on 2025-01-12. You have enabled automatic annual renewal for this domain.
You will be charged $13 USD for the renewal of the domain [1].
If you want to keep the domain, no further action is needed. On 2025-01-12, we'll charge an annual registration fee to your AWS account.
If you don't want us to renew registration for mozillafest.world, disable automatic renewal (instructions here) before 2025-01-12. If you disable automatic renewal, the domain will expire on 2025-02-16. You will receive two email reminders before expiration, as required by ICANN.
The registration price depends on the top-level domain (TLD). For more information, see AWS Route53 pricing.
For more information about managing your domain settings, see Updating settings for a domain.
Regards,
Amazon Route 53
Please ensure that the renewal is turned disabled.
┆Issue is synchronized with this Jira Bug
The text was updated successfully, but these errors were encountered: