What to do if your verification code doesn’t arrive
First, identify whether you used a temporary address or a forwarding alias. Then check the address, expiry and sending status. This page can’t check the sender’s systems, and “request submitted” doesn’t mean “delivered.”
Requesting, sending and receiving are three separate steps.
The form accepting your request doesn’t mean the website has sent an email.
The sender’s website must confirm whether it’s in the sending queue or restricted by domain rules.
For a temporary address, check the inbox; for an alias, check the forwarding archive.
Get guidance based on what you see
You don’t need to enter an email address, verification code or credentials. Your selections are used only on this page to suggest next steps. We won’t check your inbox or trigger a resend.
Address and expiry
If you’re not receiving a code at a temporary email address, first check the address you submitted—not just any address currently shown on screen.
Copy the full address from the home page, then check that the website’s form hasn’t truncated or autocorrected it or added spaces. If you entered it incorrectly, update it if the website allows and request again as instructed.
See the trial sign-up checklistIf you clicked “Get a new address” after submitting, update the address on the website. Messages sent to the old address won’t be redirected to the new one. Don’t expect an old request to appear in the new inbox.
Check your current temporary addressThe default validity period is 3 hours. Each extension adds 3 hours, up to 24 hours total. Expired addresses and emails can’t be recovered. Extending an address won’t reactivate a verification code that has expired.
Check expiry and deletion detailsSending and waiting
The inbox checks for arrived messages at most every 8 seconds. That doesn’t mean the website will send one within 8 seconds, or that transmission or forwarding will finish within that time.
Choose the right address type before waiting longerComplete any CAPTCHA, required fields or send confirmation the website asks for. If it only says “request submitted,” ask the website to confirm whether the message entered its sending queue. Rapidfwd can’t access third-party sending logs.
This is an email address policy for registration or receiving—not a refresh-frequency issue. Use an email type the website accepts, or contact its support team. A forwarding alias isn’t guaranteed to bypass domain restrictions.
Follow the website’s cooldown and resend instructions, and use only the code from your latest request. Extending your email address won’t extend the code’s validity.
Message status
Temporary inbox messages don’t appear in the forwarding archive, and alias messages don’t appear in the temporary inbox on the home page. Check the right place before deciding what to do next.
Check the current address, then look for the real sender and subject in the list. Open the message to read it; the code may be in the body rather than the subject.
First, make sure the alias is enabled. Then find the record for this request in the archive. A disabled alias won’t forward new messages, and re-enabling it won’t recover messages discarded while it was disabled.
The archive keeps records for 30 days. No record doesn’t prove the website never sent an email. You may have checked the wrong alias, the alias may have been disabled, or the record may have expired.
Resending and when to ask for help
Repeated requests may invalidate an earlier code or trigger the website’s sending limits. Don’t keep clicking resend. Wait out the cooldown shown by the website and check the timestamp on the latest email.
Contact the sender’s website first if your address is correct and hasn’t expired, but the site hasn’t confirmed sending—or says the domain isn’t supported. Only the sender can confirm its sending queue, registration restrictions and code rules.
You can provide the request time and time zone, the exact message shown by the website, whether you completed verification, and the email domain. Don’t share your Rapidfwd login credentials.
Contact support if the inbox tool shows an error, the expiry looks wrong, or a forwarding record stays failed or pending for a long time. Say whether you used a temporary inbox or an alias, and include when it happened, your time zone, browser and checks you’ve tried.
If you share a screenshot, hide unnecessary parts of the address, message body and verification code. You can include a redacted error or status screenshot to help support investigate.
Contact support@rapidfwd.comNever send verification codes, tokens, full links containing credentials, or the complete contents of sensitive messages. This page doesn’t ask for that information. Use your personal, long-term email for accounts involving banking, payments, identity documents or account recovery. Read the Privacy Policy and the Terms of Service to understand the limits.
Check the actual records
Check the address and time remaining first, then look for a real message. Don’t rely on an expiring temporary address for ongoing subscriptions or future notifications.
Choose an inbox type, then answer the relevant questions. We won’t judge whether an email was sent based on wait time or claim delivery without verification.
Some checks are incomplete. Answer every question for this inbox type. If you’re unsure about something, check the actual inbox tool or the sender’s website first.
Awaiting checks
Suggested action · Not delivery proof
Correct or confirm the address first. Check the full address and domain and remove any extra spaces. If the website lets you change the address, update it and request again according to its rules. Other checks can’t make up for an incorrect address.
You changed the address after submitting, so the old request won’t move to the new inbox. Update the website with your current address, then request a new code as instructed. Don’t expect old messages to move to the new address.
Check the home-page countdown first. If the address is still valid, you can extend it by 3 hours each time, up to 24 hours total. Expired addresses and emails can’t be recovered. After expiry, use a new address and update the request on the website.
The website has explicitly restricted this email address or domain. Refreshing, extending or switching to another address on the same domain isn’t guaranteed to help. Use an email type the website accepts, or ask the sender about its policy.
Ask the sender’s website to confirm whether the email was actually sent. Without a clear success message, a submitted request doesn’t mean it was sent. Check the website’s verification steps, errors and cooldown rules, and avoid repeated requests.
A valid inbox can’t restore an expired code. Follow the sender’s cooldown and resend instructions, and use only the email for your latest request.
You indicated that you found the real message. Open it and check the sender, purpose and expiry under the website’s rules before using the latest code. This page hasn’t independently verified the message or code.
You indicated that the archive shows the message as forwarded. Check your inbox, spam, categories and mail rules, or open the archive message. Forwarded doesn’t guarantee delivery to your primary inbox.
You indicated that the message was blocked. Open the matching archive entry and check the sender, subject and body to make sure it’s the message you need. A verification code doesn’t automatically mean a message is safe; don’t open unfamiliar links.
You indicated that forwarding failed. Check the record details and timestamp, and make sure the destination inbox is available. You can read the message in the 30-day archive. If the problem continues, contact support with redacted status and timestamp details.
You indicated that the record is pending. This doesn’t mean delivery is complete. Check the archive again later; this page can’t estimate how long processing will take. If the status doesn’t change, contact support with the request time and time zone.
There isn’t enough information to identify where delivery is delayed. For a temporary address, check the current inbox; for an alias, confirm it’s enabled and check the 30-day archive. Checking at most every 8 seconds doesn’t guarantee delivery within 8 seconds. If there’s still no record, ask the sender to confirm whether it sent the email.
Check your inbox tool
View forwarding archive
Resending and when to ask for help
Choose an inbox type and answer its questions. Waiting time alone does not prove that a message was sent or delivered.
Some checks are incomplete. Answer every question for this inbox type; verify uncertain details in the actual inbox or on the sender’s website.
Awaiting checks
Suggested action · Not delivery proof
Confirm or correct the full address and domain, removing extra spaces. If the website permits changes, update the address and request again under its rules. Other checks cannot compensate for an incorrect address.
You changed the address after submitting. The old request will not move to the new inbox. Update the website with the current address before requesting a new code.
Check the countdown first. While valid, each extension adds 3 hours, up to 24 hours in total. Expired addresses and messages cannot be restored; use a new address and update the request.
The website restricts this address or domain. Refreshing, extending or switching within the same domain is not a guaranteed fix. Use an accepted mailbox type or ask the sender about its policy.
Ask the sender whether a message was actually sent. A submitted request is not a sending confirmation. Check verification steps, errors and cooldown rules before requesting again.
A valid mailbox cannot revive an expired code. Follow the sender’s cooldown and resend instructions, then use only the message for the latest request.
You reported finding the real message. Open it and check the sender, purpose and code validity before using the latest code. This page has not independently verified authenticity or validity.
You reported a forwarded archive entry. Check your own inbox, spam, categories and mail rules, or read the archive body. Forwarded does not guarantee placement in the primary inbox.
You reported a blocked message. Open the matching archive entry and check sender, subject and body. A message containing a code is not automatically safe; avoid unfamiliar links.
You reported a forwarding failure. Check the details, timestamp and destination mailbox. You may read the body in the 30-day archive; contact support with redacted status information if the problem persists.
You reported a pending entry. Processing is not complete; check the archive again later. This page cannot estimate completion. Contact support with the request time and time zone if it remains unchanged.
There is not enough evidence to locate the delay. Check the current temporary inbox, or confirm the alias is enabled and inspect its 30-day archive. Polling at most every 8 seconds is not an 8-second delivery promise. Ask the sender to confirm sending if no record appears.
Check the actual inbox
View forwarding archive
Resending and support limits
Choose an inbox type and answer its questions. Waiting time alone does not prove that a message was sent or delivered.
Some checks are incomplete. Answer every question for this inbox type; verify uncertain details in the actual inbox or on the sender’s website.
Awaiting checks
Suggested action · Not delivery proof
Confirm or correct the full address and domain, removing extra spaces. If the website permits changes, update the address and request again under its rules. Other checks cannot compensate for an incorrect address.
You changed the address after submitting. The old request will not move to the new inbox. Update the website with the current address before requesting a new code.
Check the countdown. Before expiry, each extension adds 3 hours, up to 24 hours total. An expired address and its messages can’t be recovered; use a new address.
The website doesn’t accept this address or domain. Refreshing, extending or changing to another address on the same domain won’t guarantee a fix. Use an accepted address type or ask the website about its policy.
Ask the website whether the message was actually sent. Submitting a request doesn’t confirm that it was sent. Check verification steps, errors and the cooldown before trying again.
An inbox that’s still valid won’t reactivate an expired code. Follow the website’s cooldown and resend instructions, then use only the message for your latest request.
You said you found the real message. Open it and check the sender, purpose and code validity. This page doesn’t verify its authenticity or validity.
You said the archive marks the message as forwarded. Check your inbox, spam, categories and mail rules, or read the archived message. This status doesn’t guarantee delivery to your primary inbox.
You said the message was blocked. Open the matching archive entry and check the sender, subject and content. A code doesn’t guarantee the message is safe; avoid unfamiliar links.
You said forwarding failed. Check the details, time and destination inbox. The message can be read in the 30-day archive. If the problem persists, contact support with redacted information.
You said the record is pending. Delivery isn’t complete; check the archive again later. This page can’t estimate how long it will take. If the status doesn’t change, contact support with the request time and time zone.
There isn’t enough information to identify where delivery is delayed. Check the current temporary inbox, or make sure the alias is enabled and check its 30-day archive. Checking at most every 8 seconds doesn’t guarantee delivery within 8 seconds. If there’s no record, ask the sender to confirm whether it sent the email.
Check the actual inbox
View archive
Resending and support
Choose an inbox type and answer its questions. Waiting time alone does not prove that a message was sent or delivered.
Some checks are incomplete. Answer every question for the selected inbox type, and verify anything uncertain in the actual inbox or on the sender’s website.
Awaiting checks
Suggested next step · Not proof of delivery
Confirm or correct the full address and domain, removing any extra spaces. If the website allows changes, update the address and request again according to its rules. Other checks can’t make up for an incorrect address.
You changed the address after submitting. Messages from the old request won’t move to the new inbox. Update the address on the website before requesting a new code.
Check the time remaining first. Each extension adds 3 hours while the address is valid, up to 24 hours total. Expired addresses and emails can’t be restored. Update the request with a new address.
The website restricts this address or domain. Refreshing, extending or changing to another address on the same domain isn’t guaranteed to help. Use an accepted email address or ask the website about its policy.
Ask the website whether the email was actually sent. A submitted request doesn’t mean it was sent. Check the verification steps, errors and resend cooldown, and don’t make repeated requests.
A valid inbox can’t revive an expired code. Follow the website’s cooldown and resend instructions, and use only the message for your latest request.
You indicated that you found the real message. Open it and check the sender, purpose and validity before using the latest code. This page hasn’t verified the message’s authenticity or the code’s validity.
You indicated that the archive marks the message as forwarded. Check your inbox, spam, categories and mail rules, or open the archived message. Forwarded doesn’t guarantee delivery to your primary inbox.
You indicated that the message was blocked. Open the matching archive entry and check the sender, subject and body. A code doesn’t automatically mean it’s safe; don’t open unfamiliar links.
You indicated that forwarding failed. Check the details, timestamp and destination inbox. You can read the message in the 30-day archive. If the problem persists, contact support with redacted status details.
You indicated that the record is pending. Delivery isn’t complete; check the archive again later. This page can’t estimate when it will finish. If the status doesn’t change, contact support with the request time and time zone.
There isn’t enough information to identify where delivery is delayed. Check the current temporary inbox, or confirm the alias is enabled and check its 30-day archive. Checking at most every 8 seconds doesn’t guarantee delivery within 8 seconds. If no record appears, ask the sender to confirm whether it sent the email.
Check the actual inbox
View forwarding archive
Resending and support guidelines
Choose an inbox type and answer its questions. Waiting time alone does not prove that a message was sent or delivered.
Some checks are incomplete. Answer every question for this inbox type and check any uncertainties in the actual inbox or on the sender’s website.
Awaiting checks
Suggested next step · Not proof of delivery
Confirm or correct the full address and domain, removing extra spaces. If the website allows changes, update the address and request again according to its rules. Other checks can’t correct an incorrect address.
You changed the address after submitting. The old request won’t move to the new inbox. Update the address on the website before requesting a new code.
Check the countdown. While the address is valid, each extension adds 3 hours, up to 24 hours total. Expired addresses and emails can’t be recovered; use a new address and update the request.
The website restricts this address or domain. Refreshing, extending or switching to another address on the same domain isn’t guaranteed to help. Use an accepted inbox type or check the website’s policy.
Ask the website to confirm whether the message was actually sent. A submitted request doesn’t prove it was sent. Check verification steps, errors and cooldowns before trying again.
An inbox that’s still valid can’t restore an expired code. Follow the website’s cooldown and resend instructions, and use only the message for your latest request.
You said you found the real message. Open it and check the sender, purpose and validity before using the latest code. This page hasn’t verified its authenticity or validity.
You said the archive shows a forwarded message. Check your inbox, spam, categories and mail rules, or read the archived message. Forwarded doesn’t guarantee delivery to your primary inbox.
You said the message was blocked. Open the matching archive entry and check the sender, subject and content. A code doesn’t guarantee a message is safe; avoid unfamiliar links.
You said forwarding failed. Check the details, time and availability of the destination inbox. You can read the message in the 30-day archive. If the problem persists, send support redacted status details.
You said the record is pending. That doesn’t mean delivery is complete; check the archive again later. This page can’t estimate the wait. If the status doesn’t change, contact support with the request time and time zone.
There isn’t enough evidence to identify where delivery is delayed. Check the current temporary inbox, or confirm the alias is enabled and check its 30-day archive. Checking at most every 8 seconds doesn’t guarantee delivery within 8 seconds. If no record appears, ask the sender to confirm whether it sent the email.
Check the actual inbox
View forwarding archive
Resending and support limits
