mapleyellow.com - dns.ninja
mapleyellow.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 153.126.186.5🇯🇵 SAKURA-A153.126.128.0/17 (ISHIKARI) SAKURA Internet // HOKKAIDO JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | mapleyellow.com | ||||||
| NS | ns1.myasp.jp ⭐ | ||||||
| A | 153.126.139.23🇯🇵 SAKURA-A153.126.128.0/17 (ISHIKARI) SAKURA Internet // HOKKAIDO JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | 18.myasp-ao.com | ||||||
| NS | ns2.myasp.jp | ||||||
| A | 153.126.149.128🇯🇵 SAKURA-A153.126.128.0/17 (ISHIKARI) SAKURA Internet // HOKKAIDO JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | 19.myasp-ao.com | ||||||
| MX | mapleyellow.com ⭐ | ||||||
| A | 153.126.186.5🇯🇵 SAKURA-A153.126.128.0/17 (ISHIKARI) SAKURA Internet // HOKKAIDO JAPAN BACKBONE Sakaisuji Honmachi Bldg. 9F 1-8-14 Minami-Honmachi, Chuo-ku Osaka 541-0054, Japan | ||||||
| PTR | mapleyellow.com | ||||||
| TXT | v=spf1 +mx include:myasp.jp ~all | ||||||
| SOA | ns1.myasp.jproot@mapleyellow.com 2024-09-24 #2 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1783760867 | ||||||
PTR for
MX for
mapleyellow.com |
Same first word
mapleyellow.com |
Similar names
DNS History
22 records (4 active, 18 former)
○NSns-cloud-b1.googledomains.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○NSns-cloud-b2.googledomains.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○NSns-cloud-b3.googledomains.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○NSns-cloud-b4.googledomains.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○NSns1.m51.siteground.biz2016-09-21 → 2016-09-21 · 4 obs
○ 2016-03-13 21:56:42
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
●NSns1.myasp.jp2026-03-26 → 2026-07-11 · 3 obs
○ 2017-06-04 08:12:24
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
○NSns1.siteground242.com2015-08-22 → 2016-03-13 · 4 obs
● 2015-08-22 13:07:22
● 2016-03-13 21:56:42
○ 2016-09-21 10:10:04
○ 2026-07-11 09:26:20
● 2016-03-13 21:56:42
○ 2016-09-21 10:10:04
○ 2026-07-11 09:26:20
○NSns2.m51.siteground.biz2016-09-21 → 2016-09-21 · 4 obs
○ 2016-03-13 21:56:42
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
●NSns2.myasp.jp2026-03-26 → 2026-07-11 · 3 obs
○ 2017-06-04 08:12:24
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
○NSns2.siteground242.com2015-08-22 → 2016-03-13 · 4 obs
● 2015-08-22 13:07:22
● 2016-03-13 21:56:42
○ 2016-09-21 10:10:04
○ 2026-07-11 09:26:20
● 2016-03-13 21:56:42
○ 2016-09-21 10:10:04
○ 2026-07-11 09:26:20
○MXalt1.gmr-smtp-in.l.google.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○MXalt2.gmr-smtp-in.l.google.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○MXalt3.gmr-smtp-in.l.google.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○MXalt4.gmr-smtp-in.l.google.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
○MXgmr-smtp-in.l.google.com2017-06-04 → 2017-06-04 · 4 obs
○ 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
●MXmapleyellow.com2026-03-26 → 2026-07-11 · 3 obs
○ 2017-06-04 08:12:24
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
○MXmx10.mailspamprotection.com2015-08-22 → 2016-09-21 · 4 obs
● 2015-08-22 13:07:22
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
○MXmx20.mailspamprotection.com2015-08-22 → 2016-09-21 · 4 obs
● 2015-08-22 13:07:22
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
○MXmx30.mailspamprotection.com2015-08-22 → 2016-09-21 · 4 obs
● 2015-08-22 13:07:22
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
● 2016-09-21 10:10:04
○ 2017-06-04 08:12:24
○ 2026-07-11 09:26:20
○A109.73.236.1372016-09-21 → 2017-06-04 · 5 obs
○ 2016-03-13 21:56:42
● 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
● 2016-09-21 10:10:04
● 2017-06-04 08:12:24
○ 2026-03-26 10:30:00
○ 2026-07-11 09:26:20
●A153.126.186.52026-03-26 → 2026-07-11 · 3 obs
○ 2017-06-04 08:12:24
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
● 2026-03-26 10:30:00
● 2026-07-11 09:26:20
○A181.224.136.1682015-08-22 → 2016-03-13 · 4 obs
● 2015-08-22 13:07:22
● 2016-03-13 21:56:42
○ 2016-09-21 10:10:04
○ 2026-07-11 09:26:20
● 2016-03-13 21:56:42
○ 2016-09-21 10:10:04
○ 2026-07-11 09:26:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| mapleyellow.com | ns1.myasp.jp, ns2.myasp.jp | - |
✅ Authoritative Response
Server:153.126.139.23
NS records: ns1.myasp.jp, ns2.myasp.jp
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for mapleyellow.com (unsigned zone)
⏱️ Timing
Total: 977ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 153.126.186.5 |
| NS | 2 | ns1.myasp.jp, ns2.myasp.jp |
| MX | 1 | mapleyellow.com (pri: 10) |
| TXT | 1 | v=spf1 +mx include:myasp.jp ~all |
| SOA | 1 | ns1.myasp.jp root.mapleyellow.com |
Analysis
Mail Server Role
mapleyellow.com is listed as a mail server for itself.
IP Addresses
mapleyellow.com resolves to one IP address: 153.126.186.5.
Host names like ik1-329-24501.vs.sakura.ne.jp are further examples that share IP numbers with mapleyellow.com.
Name Servers
Two name servers handle the delegation for mapleyellow.com: ns1.myasp.jp and ns2.myasp.jp.
mapleyellow.com uses the same name servers as several other domains — among them kame-sensei.com, yuki-movie.com, tsugumin.com and two more.
ns1.myasp.jp → 153.126.139.23 and ns2.myasp.jp → 153.126.149.128: one IP number per host name.
Mail Servers
Mail for mapleyellow.com is handled by one mail server — mapleyellow.com.
mapleyellow.com carries a single IP number, which is 153.126.186.5.