Help • Notification emails

Email from Basefund

How to ensure Basefund email reaches you and how to sign in without waiting on it.

Every account and transaction email from Basefund is sent from

notifications@secure.basefund.com

Sign-in codes, closing invitations, reminders, and account notices all come from this one address. Go by the address, not the sender name, which can read slightly differently from one kind of message to another. If you or your IT team keep a list of trusted senders, this is the address to put on it.

Newsletters and product announcements are sent separately, from @email.basefund.com.

Sign-in codes taking too long?

You have two ways to fix this for good. Either one works on its own.

Recommended · takes one minute

Use a passkey and skip email entirely

A passkey lets you sign in with Face ID, Touch ID, Windows Hello, or your password manager. No code, no inbox, no waiting.

Sign in to Basefund as usual.
Open your Profile, then Security, then Passkeys.
Under Passkey, add one and follow your device’s prompt.
Next time, pick Sign in with a Passkey on the sign-in screen.

You can add a passkey on each device you use, and email codes keep working as a backup.

If your organization filters email

Ask IT to trust secure.basefund.com

Most delays happen inside a company’s own email security. Adding our sending domain to your organization’s trusted-sender list lets our email through without the extra holds.

Forward the For IT administrators section below to your IT or security team. It has everything they need.

Where the time goes

When you request a sign-in code, the message leaves our mail service within moments, from servers reserved for account and transaction email with a long history of clean sending. We time every one of them, from the moment the message leaves us to the moment your organization’s mail server accepts it.

2 seconds

typical time until your mail server accepts a sign-in code

9 in 10

accepted within 6 seconds

99 in 100

accepted within 30 seconds

Measured across 329 sign-in codes to 114 organizations, September 2026. Not one was refused or held by the receiving server.

Once your mail server has accepted the message, it is inside your organization’s systems, and that is where nearly all delays happen. The usual causes:

Security scanning

Tools such as Microsoft Defender, Proofpoint, and Mimecast open every link and attachment in a sandbox before releasing a message. This commonly adds 20 to 60 seconds, sometimes more.

First-contact holds

Some gateways deliberately refuse the first message from a sender they have not seen before and accept it on retry about 10 minutes later. The first Basefund email to your organization may be slow; later ones are not.

Quarantine

If a filter quarantines the message, you may only see it in a daily quarantine digest, or not at all until an administrator releases it.

Blocked senders

An administrator may have blocked our domain, or an older Basefund address, in the past.

Sign-in codes expire 15 minutes after you request them. If a code has not arrived, request a replacement. Requesting a replacement invalidates any earlier code, so if an older one turns up later, ignore it and use the newest. Or set up a passkey and never wait on a code again.

Quick checks

Look in your Junk or Spam folder, and in any quarantine folder or digest email your organization sends.
Add notifications@secure.basefund.com to your contacts or safe-senders list.
Check that the email address on your Basefund profile is the inbox you are watching.
Request a replacement code rather than waiting on an old one. A replacement invalidates any earlier code, so always use the newest.
Set up a passkey so sign-in no longer depends on email.

For IT administrators

Basefund sends all account and transaction email from a dedicated sending domain, authenticated with SPF, DKIM, and DMARC, so your gateway can verify every message. Trust the domain rather than IP addresses: our mail leaves from a pool of authenticated servers whose addresses can change, and we do not publish them.

Account and transaction email	`notifications@secure.basefund.com` · sending domain `secure.basefund.com`
Newsletters	sent from `@email.basefund.com`, on separate infrastructure
Envelope sender	If your policies match the envelope (return-path) domain rather than the From header, read it from the `Return-Path` header of any message we have sent you, or ask support@basefund.com.
Authentication	SPF and DKIM pass with DMARC alignment on every message
Link rewriting	“External sender” banners and link-rewriting tools do not affect delivery

Your organization’s security screening software

Microsoft 365	Add `secure.basefund.com` as an allowed sender domain in your anti-spam policy or the Tenant Allow/Block List. Safe Attachments and Safe Links scanning still adds a short delay; that is expected.
Mimecast	Add a Permitted Senders entry for `secure.basefund.com`, and a Greylisting bypass so first messages are not held. Include the envelope domain if your policy keys on it.
Proofpoint	Add `secure.basefund.com` to your organizational safe-sender list.
Google Workspace	Add `secure.basefund.com` to the approved senders list in your spam settings.

Basefund never sends from personal addresses and never asks anyone to share a sign-in code.

What we do on our side

Account and transaction email is sent from its own domain and its own servers, separate from any newsletter or marketing mail, so nothing else can affect its reputation.
Every message is signed and authenticated so receiving systems can confirm it came from us.
We track every delivery and retry automatically whenever a mail server asks us to try again later.
If your mail server tells us it has accepted a message, we can tell you exactly when.

Still not receiving our email?

Email support@basefund.com with the email address on your account and roughly when you expected the message. If your IT team has the message headers of an email that arrived late, include those too. We can see the moment your mail server accepted each message, which usually settles where the delay is within minutes.