Email server settings
@nifty SMTP, IMAP & POP3 settings
Use these settings to add your @nifty account (nifty.com) to Outlook, Apple Mail, Thunderbird, your phone or any app that sends email over SMTP.
Incoming mail
POP3
- Server
- pop.
nifty. com - Port
- 110
- Security
- None (unencrypted)
- User name
- part before the @
- Authentication
- Encrypted password
Outgoing mail
SMTP
- Server
- smtp.
nifty. com - Port
- 587
- Security
- None (unencrypted)
- User name
- part before the @
- Authentication
- Encrypted password
How to set up @nifty in a mail app
- Choose add account → manual setup (or “other account”) in your mail app.
- Enter your full @nifty email address and password.
- Pick POP3 for incoming mail and enter the server, port and security from the table above.
- Enter the SMTP server for outgoing mail (smtp.nifty.com, port 587) and enable authentication with the same login.
If the login keeps failing, check that IMAP/POP access is enabled in the @nifty web settings, and use an app password if your account uses two-step verification.
Settings from the Mozilla Thunderbird ISP database (MPL 2.0), which mail clients use for automatic setup.
@nifty email settings: FAQ
What is the @nifty SMTP server?
Why does my @nifty login fail in a mail app?
Email validation API
Validate nifty.com addresses before you send
emailvalidation.io checks syntax, MX records and the mailbox over SMTP, flags disposable, role and free addresses and returns a quality score, in one request.
/v1/info Email validation API Read the documentation
100 free validations every month. No credit card required.
GET https://api.emailvalidation.io/v1/info?
{
"email": "support@emailvalidation.io",
"user": "support",
"tag": "",
"domain": "emailvalidation.io",
"format_valid": true,
"mx_found": true,
"smtp_check": true,
"catch_all": null,
"role": true,
"disposable": false,
"free": false,
"score": 0.64,
"state": "deliverable",
"reason": "low_quality",
"did_you_mean": "",
"catch_all_resolution": null,
"bounce_probability": null,
"status": "valid",
"sub_status": "role_based",
"explanation": "The mailbox exists, but it is a role address (such as info@ or support@), usually read by a team rather than one person.",
"recommended_action": "send_with_caution"
}