☰

nifty.com

IP address 76.223.106.131
Mail Configured
Records 22

The domain nifty.com answers at IP address 76.223.106.131. Mail for nifty.com goes through 1 servers; the highest priority one is mx2.nifty.com. It also publishes 15 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.

A A records

MX MX records

NS NS records

TXT TXT records

  • amazonses:0QGA5rdeHo3NPrL3ycYJP5VukcFE8YK2HJLfGYZU2wo= 3054s
  • google-site-verification=KiXiyOAC7zoylK_N-vmVqLJmY2um1kHJaX5rGKS0hN4 3054s
  • amazonses:RRh4iVzSCRb3ITrbbu8V46UQdPSwH3CCbn1dnlNwhZY= 3054s
  • _rb2xriu5nwfw4wc1zvqdj0np55z3zwd 3054s
  • amazonses:4Mrusw3/TJpXnU7irQ3zMR95XR0tR523krDFhzlPv1A= 3054s
  • amazonses:AgLuT5ebNqSd2VBOj5sGCKxGa8Z0cwxwNMiabIO6mp8= 3054s
  • amazonses:xRgjqp3xaQ3BnO68RIh2Pzt2L+d/RRAuk9U8gNd9ZvM= 3054s
  • google-site-verification=ezSKxSA1s-PIl5RlBNDiMGoOEkBOR1fBLfNCdh-lfoU 3054s
  • amazonses:CgfSxQANS31ZqzUKWFgdv349cU2HgbOsTJmdLOXG29E= 3054s
  • amazonses:hf8y8vy4CAlr66Rw7MdE/oyteayP3SMPcf4RDCI1d2A= 3054s
  • amazonses:nFpQ+iAcVdp3M2k8zO2PwIHHTSjRXF+0O2kfRpJ7Mow= 3054s
  • amazonses:/Alan0ux6gDkyvsSJJHLEa4vsS6g5Xi8qeDoXqOKrxI= 3054s
  • uCpabknftnCQtbkinUN4Hf7Y6wtzZo 3054s
  • amazonses:LBQr5qJRUcyIqPw5ahJ3HBOw4vxdQeutrSUHnOLXYVU= 3054s
  • 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 3054s

SOA SOA records

  • odns0.nifty.ad.jp 3600s

What each record means

  • A and AAAA: the server IP address, in IPv4 and IPv6.
  • MX: the servers that receive the domain mail. The number is the priority; the lowest is tried first.
  • NS: the name servers, which have the final say over the domain DNS.
  • TXT: free text. Mostly used for SPF, DKIM and DMARC, and to verify ownership with third parties.
  • TTL: how many seconds the record may be cached before asking again.

Checked 3 hours ago.