tkc.co.jp
IP address
—
DNS managed by
Akamai
Mail
Configured
Records
20
The domain tkc.co.jp answers at IP address —. The domain DNS is managed by Akamai, which decides where each subdomain points. Mail for tkc.co.jp goes through 1 servers; the highest priority one is prftcm-mx.tkc.co.jp. It also publishes 12 TXT records, used to verify domain ownership with external services and to configure mail security through SPF, DKIM and DMARC.
MX MX records
- 10 prftcm-mx.tkc.co.jp 2960s
NS NS records
- a1-128.akam.net 3600s
- a13-66.akam.net 3600s
- a28-64.akam.net 3600s
- a5-64.akam.net 3600s
- a14-64.akam.net 3600s
- a18-67.akam.net 3600s
TXT TXT records
- adobe-idp-site-verification=6da1fb08e6ed7f91b806ef714ce55893ba6baa49475abec19d5129b5b4623d56 60s
- ciscocidomainverification=48e97115cd2b91b3171310b6097ff1fa5de1d148971eeaa3e4a90584e0c87194 60s
- pardot385522=4816dc10bd98f6f154ab4c7ab53a58f1bdd317a1b6401ab12219f1bf3654a85a 60s
- canva-site-verification=d-Z3WmJAcEB2ACx5P_nt9Q 60s
- v=spf1 include:spf.tkc.jp include:spf.protection.outlook.com include:spf.repica.jp include:aspmx.pardot.com include:smp.ne.jp include:amazonses.com +ip4:202.32.58.20 +ip4:202.32.58.21 ~all 60s
- apple-domain-verification=DF0y9Sd3Z1KN4NaB 60s
- d365mktkey=5HUDD22sk5Tox4GX1cKzKN4MNIqxs8AjK8xPnlOFZ6Ex 60s
- google-site-verification=jYMgeC40wV8oMQyZ6iSjD-m6xe-1_7zXlKH8BrBm2mk 60s
- MS=ms55175556 60s
- google-site-verification=g514_ay_4YQXVs5yvrEMxGdqWFKhP81nWpZmgehPFhA 60s
- figma-domain-verification=e70806914056374a82d91faf9674eee8ecdd6ac3cf191600e4b3f09415aaf5b4-1743728230 60s
- anthropic-domain-verification-1rdrz2=R5nm2RpjnfYIrBTmw8AcDcGlF 60s
SOA SOA records
- a1-128.akam.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.