☰

nhk.or.jp

IP address —
Mail Configured
Records 22

The domain nhk.or.jp answers at IP address —. Mail for nhk.or.jp goes through 1 servers; the highest priority one is mx.securemx.jp. It also publishes 17 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.

MX MX records

NS NS records

TXT TXT records

  • slack-domain-verification=SUPXb8Sc7Rmcs4y8M7T3zjjF68ckNzRBdltYlSPp 300s
  • g3d1UnfgpqyGSyaaZLTlqR1Xz1TEq8 300s
  • google-site-verification=vKNqH8y1RyR-BDPhQswIuwpzpySTZgX7jTp75vw6nnY 300s
  • zoho-verification=zb22764170.zmverify.zoho.jp 300s
  • asv=92773090f6c8472811cb6e544598e3d6 300s
  • v=spf1 +ip4:133.127.68.0/24 +ip4:133.127.64.128/25 +ip4:133.127.69.160/27 +ip4:133.127.66.64/26 +ip4:210.196.154.64/29 +ip4:54.168.36.84/32 include:spf.securemx.jp include:spf-dr.securemx.jp include:relay.nhk.or.jp include:amazonses.com ~all 300s
  • nulab-verification-code=nKiDLtMAx8gW6tjiTnRHohhA3su4YMsW8L9B2T7ay85bQgfMRFIdBKSL2NpdUHLt 300s
  • adobe-idp-site-verification=f1c48c8b-04db-4bd2-9508-bcc5b00f9927 300s
  • apple-domain-verification=dKnvVgRmv2m9w0s4 300s
  • _f6tdzcm11im78xd7q3yvdg8r6ns5jlz 300s
  • notion-domain-verification=M6LdxRbYGOxsfYpqTbmo5PvqlmAkxHJ3vG8KRRlcf25 300s
  • google-site-verification=LeFONyWx2bjn4lY3vm2LmIbagQe2lSlM8KsQHqwDArQ 300s
  • adobe-idp-site-verification=1bc0d55d9832d11825c55bc9783476bed9ed9efb4ff34f9d6270837ae5447159 300s
  • MS=ms66906996 300s
  • facebook-domain-verification=d0f9pf7vgu2r4w1ofbid054vv4x46r 300s
  • 278otoK50uMcEizlzPMPYko6p5KiQA 300s
  • i0RGM31kL4XPtTgwjr2oRRWMP0sjS5 300s

SOA SOA records

  • ns.nhk.or.jp 300s

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 4 hours ago.