Signing emails from your address, through your provider
Invitations that come from your own domain get opened. Connect the email service you already use and sign.yt sends every notification through it.
Pick the provider you already trust
Start with managed delivery and nothing to configure. When you are ready, switch your organization to your own SMTP server, Microsoft 365 through the Graph API, your own Resend account, Amazon SES or Mailgun.
Provider credentials are stored encrypted, never in plain text.
Each organization picks one provider, so every invitation, reminder and completion email goes out the same way.
Microsoft 365 without SMTP passwords
With the Graph API, sign.yt sends as a mailbox in your Microsoft 365 tenant using an Azure app registration with the Mail.Send permission. No SMTP password to store, and no basic authentication to keep enabled in your tenant.
You choose the sending address, for example contracts@yourcompany.com, so replies from recipients reach a real mailbox your team already watches.
DNS records checked for you
The settings screen lists the SPF, DKIM and DMARC records your sender domain needs for the chosen provider, then looks them up live and shows which are in place. Fewer invitations end up in spam.
Amazon SES DKIM records are fetched for your domain automatically, and for other providers the screen tells you exactly which values to copy into your DNS panel.
Bounces do not go unnoticed
With managed delivery, bounced and spam-flagged emails mark the recipient as bounced, are written to the audit log and trigger a recipient.bounced webhook, so you can fix the address instead of waiting for a signature that will never come.
The same bounce information is visible on the document, next to the recipient. You find out as soon as the provider reports it, not after the signing deadline has passed.
Frequently asked questions
Which email providers are supported?
Managed delivery, SMTP, Microsoft 365 via Graph API, Resend with your own account, Amazon SES and Mailgun.
Which SMTP ports can I use?
Ports 25, 465, 587 and 2525, with TLS.
Can teams use different sender names?
Yes. The sender name can be set per team through team branding.
Do I have to configure anything to start?
No. Managed delivery works out of the box; your own provider is optional.
More features
- Custom domains
Run e-signatures on your own domain, like sign.yourcompany.com. Point one CNAME record, we verify DNS and issue the TLS certificate automatically.
- White-label branding
Your logo, colours and one of four page themes on every signing page, verification page and email. Teams can have their own look, or you lock it.
- Document templates
Save contracts as templates with signers and fields in place. Reuse them in seconds, swap the PDF when the wording changes, or share a public signing link.