rakuten-card.co.jp
The domain rakuten-card.co.jp answers at IP address 23.67.138.175. That address belongs to Akamai International, BV, based in Germany. The domain DNS is managed by Akamai, which decides where each subdomain points. Mail for rakuten-card.co.jp goes through 3 servers; the highest priority one is mail-receive-00.rakuten-card.co.jp. 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
- 23.67.138.175 20s
AAAA AAAA records
MX MX records
- 5 mail-receive-00.rakuten-card.co.jp 3372s
- 10 reml01.rakuten-card.co.jp 3372s
- 10 reml02.rakuten-card.co.jp 3372s
NS NS records
- a4-65.akam.net 3600s
- a9-64.akam.net 3600s
- a10-67.akam.net 3600s
- a6-66.akam.net 3600s
- a1-138.akam.net 3600s
- a3-64.akam.net 3600s
TXT TXT records
- google-site-verification=TnoxHLt7xBw_4UNGiZis7YhUud98MlUmOtavRApn788 21600s
- 0bq36dlry7cvsbbybmwyllss8wgqdm9k 21600s
- dwqdh2mh2r9zp5cd24k2dykwmp1gs2px 21600s
- apple-domain-verification=4LosIqAYvFeWsZsT 21600s
- _a1cq745okdtfl44usndtaesv3pnlb9p 21600s
- 937k8dghztdp4tj59jq213f9v5gp5gjg 21600s
- v=spf1 include:spf-bma.mpme.jp include:spf01.rakuten-card.co.jp include:spf02.rakuten-card.co.jp include:spf03.rakuten-card.co.jp ~all 21600s
- google-site-verification=TGyEmsq1HwB6oBaVmWG_x5nOOLrYzwKhr1jXSZFZA4M 21600s
- google-site-verification=2FDJ1jO6p9crn9OZU1uFZJ-PEhANPqtJP3FaEziT6YU 21600s
- syxnyh9zshf969lkszyb08q9p50x1s14 21600s
- _1lufyuoaem2lpqaqgegjg9voxam99l1 21600s
- google-site-verification=nEgN8-AEunZ-r3OsqCHWqtlgaIyuyo0yR81z79Jq9ek 21600s
- j96fwz0kyp78ns5pnbq6d9zjjffbcp86 21600s
- _g2h27bs0oxoj5jmcmyex9z0c7h88lq1 21600s
- vfvty6bw0vpd2wd4hh2czrg8fs8gyqdk 21600s
SOA SOA records
- a1-138.akam.net 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 20 hours ago.