ttapp.jp - robtex.com
ttapp.jp
jp
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | z.dns.jp ⭐ | ||||||
| NS | a.dns.jp | ||||||
| NS | b.dns.jp | ||||||
| NS | c.dns.jp | ||||||
| NS | d.dns.jp | ||||||
| NS | e.dns.jp | ||||||
| NS | f.dns.jp | ||||||
| NS | g.dns.jp | ||||||
| NS | h.dns.jp | ||||||
| SOA | z.dns.jproot@dns.jp serial=1771290902 | ||||||
Same first word
Similar names
ptatp.gov.la |
apptt.com |
pttap.com |
patpt.info |
tappt.net |
tappt.com |
tappt.co |
ppatt.com |
pptat.com |
tpatp.ru |
ptpat.com |
apttp.com |
atppt.com |
ptapt.com |
patpt.net |
pptta.com |
ptatp.co.id |
ttppa.org.tw |
tappt.org |
DNS History
13 records (13 active, 0 former)
●NSns-1527.awsdns-62.org2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●NSns-1749.awsdns-26.co.uk2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●NSns-353.awsdns-44.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●NSns-932.awsdns-52.net2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●MXalt1.aspmx.l.google.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●MXalt2.aspmx.l.google.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●MXalt3.aspmx.l.google.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●MXalt4.aspmx.l.google.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●MXaspmx.l.google.com2026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●A3.162.103.182026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●A3.162.103.582026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●A3.162.103.612026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
●A3.162.103.782026-02-27 → 2026-02-27 · 2 obs
● 2026-02-27 03:54:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | 15 records |
| ttapp.jp | ns-353.awsdns-44.com, ns-932.awsdns-52.net, ns-1527.awsdns-62.org, ns-1749.awsdns-26.co.uk | - |
✅ Authoritative Response
Server: 205.251.193.97
NS records: ns-353.awsdns-44.com, ns-932.awsdns-52.net, ns-1527.awsdns-62.org, ns-1749.awsdns-26.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ttapp.jp (unsigned zone)
⏱️ Timing
Total: 1753ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 4 | 3.162.103.61, 3.162.103.58... |
| NS | 4 | ns-1527.awsdns-62.org, ns-1749.awsdns-26.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=RTR2h48ZHU4lge7, google-site-verification=aM5tVHIVteJbZiN |
| SOA | 1 | ns-1749.awsdns-26.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 15
In-bailiwick: 15 (a.dns.jp, a.dns.jp, b.dns.jp...)
AI analysis
ttapp.jp refers to four IP numbers: 3.162.103.18, 3.162.103.58, 3.162.103.61 and 3.162.103.78.
Other host names, for instance knee-omiya.net, www.curiously.co.uk, renderpool.net, m-gs.kr and d3hq7q2yvo9d6m.cloudfront.net share IP numbers with ttapp.jp.
ttapp.jp delegates to four name servers: ns-353.awsdns-44.com, ns-932.awsdns-52.net, ns-1527.awsdns-62.org and ns-1749.awsdns-26.co.uk.
ttapp.jp at least partially shares name servers with other domains, including d8ewr8juxqro5.cloudfront.net, zectorprotest.com, ac.on.ballybet.ca, vitesseinside.nl and 24fd.com.
These name servers are commonly used with ns-261.awsdns-32.com, ns-653.awsdns-17.net, ns-1856.awsdns-40.co.uk, a.ns.campaign.adobe.com, b.ns.campaign.adobe.com, c.ns.campaign.adobe.com, d.ns.campaign.adobe.com, ns-479.awsdns-59.com, ns-943.awsdns-53.net and ns-1390.awsdns-45.org.
Host names with two IP numbers: ns-353.awsdns-44.com points to 2600:9000:5301:6100::1 and 205.251.193.97; ns-932.awsdns-52.net points to 2600:9000:5303:a400::1 and 205.251.195.164; ns-1527.awsdns-62.org points to 2600:9000:5305:f700::1 and 205.251.197.247; ns-1749.awsdns-26.co.uk points to 2600:9000:5306:d500::1 and 205.251.198.213.
ttapp.jp is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
ttapp.jp shares at least some mail servers with other domains, for example ns500599.ns500599.ns500737.ns500737.ns500599.ns500724.ns500724.ns500599.ns500737.ns500737.ns500737.ns500682.ns500669.ns500669.yummyflingsfinder.com, ns500742.ns500731.ns500754.ns500731.ns500671.ns500754.ns500649.ns500666.lustychickser.com, ns500765.ns500699.ns500699.ns500734.ns500699.ns500699.ns500699.ns500693.ns500699.ns500693.ns500632.ns500632.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500765.ns500734.ns500693.ns500699.ns500699.ns500734.ns500699.ns500693.ns500693.ns500588.ns500588.ns500632.ns500588.ns500588.ns500588.ns500588.ns500588.dtrkdll.com and ns500693.ns500693.ns500699.ns500699.ns500734.ns500699.ns500693.ns500693.ns500588.ns500693.ns500699.ns500588.ns500632.ns500632.ns500588.ns500588.dtrkdll.com.
these mail servers are often used with aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to: 2607:f8b0:4004:c19::1b and 172.253.62.27.
alt1.aspmx.l.google.com points to: 2607:f8b0:4003:c30::1b and 74.125.27.26.
alt2.aspmx.l.google.com points to: 2607:f8b0:4001:c70::1a and 192.178.209.26.
alt3.aspmx.l.google.com points to: 2607:f8b0:4024:c0d::1b and 192.178.152.26.
alt4.aspmx.l.google.com points to: 2607:f8b0:4023:403::1a and 142.250.96.27.