☰
EN
Android iOS

jal.co.jp

IP address 18.178.219.162
Mail Configured
Records 23

The domain jal.co.jp answers at IP address 18.178.219.162. Mail for jal.co.jp goes through 5 servers; the highest priority one is aspmx.l.google.com. It also publishes 13 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

  • google-site-verification=rRfodkQxQk2wAkKY7D1q5fR5K7b-n2RwFKdoDmu7zMw 900s
  • google-site-verification=QTuZwFHnecpX3OO3FD6qPSqYfXvMSJoORRIPq2rCago 900s
  • google-site-verification=TwpQX5iS_zhNDi9MZNOOqDhZ1Ej7A8M1EcHjiNu6jGQ 900s
  • v=verifydomain MS=ms88274924 900s
  • fastly-domain-delegation-H7s9jh78HnIUoImziop9k-20240215 900s
  • google-site-verification=_Drief9KrSwo9Ct8K5g01DkDH6w9WvNUeSrXNxEtzTA 900s
  • google-site-verification=DpMMzCjEM4CXmLjaCmInOsmSEKeSstVty_DfVrAf774 900s
  • google-site-verification=yhoOj0H0fH2H0nXI8wiklB9wc6qwuzLLoilidfLP-xs 900s
  • google-site-verification=-aDG-L__l9F1XsWmUTXcoHp05mWhhfcbGkPi0bT9qYs 900s
  • google-site-verification=ap0gZxMczl6sDEUqipYYDO2u2-i81OnVKAXi-3IDwa4 900s
  • google-site-verification=tSppp1YPvoO4kygjYxuJj1N8aO4nmBfvG49lQB3iGSA 900s
  • google-site-verification=PJbIK19yn3KDob8Q6A71wNKGltXvVjHY0Y9U1Eby9d8 900s
  • v=spf1 +ip4:202.219.37.2 +ip4:163.211.251.0/24 +ip4:163.211.252.0/24 +ip4:163.211.253.0/24 +ip4:163.211.224.0/21 +ip4:27.112.104.239 +ip4:163.211.240.0/24 +ip4:202.218.104.28/30 +ip4:202.218.104.32/30 +ip4:210.152.224.237/32 +ip4:210.152.224.238/31 +ip4:210.152.224.240/30 include:_spf.google.com include:spf1.jal.co.jp include:spf.mailyl.jal.com include:_relay.amadeus.com ~all 900s

SOA SOA records

  • ns000.d-53.net 21600s

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.