talisa.jp - robtex.com
talisa.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=1785365102 | ||||||
Same first word
talisa.net |
talisa.co.za |
talisa.com.au |
talisa.eu |
talisa.de |
talisa.us |
talisa.com |
talisa.co |
talisa.org |
talisa.ru |
talisa.jp |
talisa.ca |
Similar names
DNS History
9 records (9 active, 0 former)
●NSns-1022.awsdns-63.net2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●NSns-1232.awsdns-26.org2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●NSns-1754.awsdns-27.co.uk2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●NSns-55.awsdns-06.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●MXalt1.aspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●MXalt2.aspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●MXalt3.aspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●MXalt4.aspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
●MXaspmx.l.google.com2026-06-30 → 2026-07-29 · 2 obs
● 2026-07-29 23:13:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| jp | a.dns.jp, b.dns.jp, c.dns.jp, d.dns.jp... | - |
| talisa.jp | ns-55.awsdns-06.com, ns-1754.awsdns-27.co.uk, ns-1232.awsdns-26.org, ns-1022.awsdns-63.net | - |
✅ Authoritative Response
Server:205.251.195.254
NS records: ns-55.awsdns-06.com, ns-1754.awsdns-27.co.uk, ns-1232.awsdns-26.org, ns-1022.awsdns-63.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for talisa.jp (unsigned zone)
⏱️ Timing
Total: 816ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1022.awsdns-63.net, ns-1232.awsdns-26.org... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 3 | facebook-domain-verification=31nsenhroz1, google-site-verification=NQDcZYyc-ygPoMV... |
| SOA | 1 | ns-55.awsdns-06.com awsdns-hostmaster.am |
Analysis
Name Servers
The NS records for talisa.jp point to four name servers: ns-55.awsdns-06.com, ns-1022.awsdns-63.net, ns-1232.awsdns-26.org and ns-1754.awsdns-27.co.uk.
There is at least partial name server overlap between talisa.jp and other domains — taurangaknitting.co.nz, uefahpgsyz.click, ideasalbarrio.com and two more among them.
These name servers are routinely deployed together with the name servers ns-43.awsdns-05.com.
All four hostnames — ns-55.awsdns-06.com, ns-1022.awsdns-63.net, ns-1232.awsdns-26.org and ns-1754.awsdns-27.co.uk — resolve to two IP numbers apiece: ns-55.awsdns-06.com to 205.251.192.55 and 2600:9000:5300:3700::1; ns-1022.awsdns-63.net to 205.251.195.254 and 2600:9000:5303:fe00::1; ns-1232.awsdns-26.org to 205.251.196.208 and 2600:9000:5304:d000::1; ns-1754.awsdns-27.co.uk to 205.251.198.218 and 2600:9000:5306:da00::1.
Mail Servers
talisa.jp has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
There is at least a partial MX overlap between talisa.jp and other domains, including markettheoutdoors.com, substituicaotributaria.com, essangola.com and two others.
alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are mail servers that frequently appear together with these mail servers.
Host names that have two IP addresses:
aspmx.l.google.com maps to two IP addresses — 172.253.62.27 and 2607:f8b0:4004:c0b::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.27 and 2a00:1450:400c:c23::1b.