MX records for nifty.com
Live MX lookup for nifty.com: 1 mail host, run by an unrecognised provider.
try:
- mail hosts
- mx2.nifty.com
- provider
- other
- spf record
- v=spf1 include:spf-03.nifty.com include:spf-04.nifty.com include:spf.ess.nifcloud.com ip4:116.83.186.110 ip4:118.67.109.25 include:ccmp.nifty.com include:amazonses.com ip4:116.83.188.150 ip4:124.24.59.16 ip4:111.171.218.84 ip4:111.171.213.113 ip4:111.171.219.244 ip4:159.183.196.94 ~all
- dmarc policy
- none
- dmarc record
- v=DMARC1; p=none; pct=100; rua=mailto:[email protected],mailto:[email protected]
- disposable domain
- no
- free consumer provider
- yes
Mail servers for nifty.com
DNS lists 1 mail host for nifty.com, starting with mx2.nifty.com. Lower priority values are tried first; the rest exist for failover.
Who runs the mail
The hosts match the pattern of an unrecognised provider. The mail hosts do not match a known provider pattern, so the domain is probably self-hosted or on a smaller provider. Catch-all behaviour varies from server to server, which is exactly why a mailbox-level probe, not the MX record, decides whether an address exists.
What this means for verification
For nifty.com, verification runs the whole pipeline: syntax, live MX, the open lists, and then the SMTP handshake with the mail host, with no message ever transmitted. Each verdict carries a machine-readable reason.
More checks for nifty.com
checked 2026-09-03 · sources: live-dns 2026-09-03 · disposable-domains 2026-09-02 · free-provider-domains 2026-09-02 · mx-provider-patterns 2026-09-03
Need this at scale?
The Spaw API runs the same checks plus mailbox-level SMTP verification, batch and bulk endpoints, and list monitoring — 10 free lookups a month, no card required.