relation.com.tw - dns.ninja
relation.com.tw
com.tw
| DNSSEC | ⚠️ Not signed | ||||||
| NS | a.twnic.net.tw ⭐ ⚠️ Not in parent delegation | ||||||
| NS | anytld.apnic.net ⚠️ Not in parent delegation | ||||||
| NS | b.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| NS | c.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| NS | d.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| NS | e.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| NS | f.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| NS | g.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| NS | h.dns.tw ⚠️ Not in parent delegation | ||||||
| NS | h.twnic.net.tw ⚠️ Not in parent delegation | ||||||
| SOA | a.twnic.net.twsnw@twnic.net.tw serial=2006358394 | ||||||
Subdomains
Same first word
Similar names
DNS History
12 records (10 active, 2 former)
●NSdan.ns.cloudflare.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●NSrose.ns.cloudflare.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXalt1.aspmx.l.google.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXalt2.aspmx.l.google.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXaspmx.l.google.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXaspmx2.googlemail.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXaspmx3.googlemail.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXaspmx4.googlemail.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
●MXaspmx5.googlemail.com2015-08-19 → 2026-06-12 · 2 obs
● 2026-06-12 13:50:36
○A104.28.26.1452015-08-19 → 2016-10-08 · 4 obs
● 2016-10-08 17:38:24
○ 2017-07-01 02:57:28
○ 2026-06-12 13:50:36
○A104.28.27.1452015-08-19 → 2016-10-08 · 4 obs
● 2016-10-08 17:38:24
○ 2017-07-01 02:57:28
○ 2026-06-12 13:50:36
●A61.61.100.132026-04-26 → 2026-06-12 · 3 obs
● 2026-04-26 05:58:04
● 2026-06-12 13:50:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| tw | g.dns.tw, e.dns.tw, f.dns.tw, a.dns.tw... | - |
| relation.com.tw | rose.ns.cloudflare.com, dan.ns.cloudflare.com | - |
✅ Authoritative Response
Server:108.162.192.141
NS records: rose.ns.cloudflare.com, dan.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for relation.com.tw (unsigned zone)
⏱️ Timing
Total: 1027ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 61.61.100.13 |
| NS | 2 | dan.ns.cloudflare.com, rose.ns.cloudflare.com |
| MX | 7 | aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | dan.ns.cloudflare.com dns.cloudflare.com |
Analysis
Hierarchy
relation.com.tw serves as the parent of www.relation.com.tw and rtvpc1.relation.com.tw.
IP Addresses
relation.com.tw has exactly one IP address — 61.61.100.13.
Name Servers
relation.com.tw uses two name servers for its delegation: dan.ns.cloudflare.com and rose.ns.cloudflare.com.
The name server configuration of relation.com.tw is shared with other domains, for instance healthymama.com.au, viewsvibe.com, squashways.co.nz and two others.
relation.com.tw shares at least some of its name servers with other domains, including snap.fan, xidakaoyan.com, rameloimoveis.com.br and two others.
These name servers are frequently paired with the name servers steven.ns.cloudflare.com, hank.ns.cloudflare.com and ali.ns.cloudflare.com.
Hosts with 6 IP addresses each:
Hostname dan.ns.cloudflare.com directs to 108.162.193.108, 172.64.33.108 and 173.245.59.108 along with 3 other IP addresses.
Hostname rose.ns.cloudflare.com directs to 108.162.192.141, 172.64.32.141 and 173.245.58.141 along with 3 other IP addresses.
Mail Servers
relation.com.tw is handled by 7 mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and 4 other.
At least some of the mail servers used by relation.com.tw are shared with other domains: ns500759.ns500759.ns500698.ns500698.ns500736.ns500735.ns500698.ns500735.ns500736.ns500736.ns500698.ns500708.ns500698.ns500698.ns500619.ns500652.ns500576.trackreceptor.com, ns500693.ns500765.ns500699.ns500699.ns500734.ns500734.ns500588.ns500693.ns500699.ns500632.ns500588.ns500110.dtrkdll.com, ns500693.ns500693.ns500699.ns500734.ns500693.ns500734.ns500734.ns500699.ns500693.ns500683.ns500683.ns500632.ns500588.ns500632.ns500632.ns500110.dtrkdll.com and two others among them.
These mail servers are often deployed together with alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
aspmx4.googlemail.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
aspmx5.googlemail.com directs traffic to 172.253.157.27 and 2a00:1450:400c:c23::1b.
aspmx.l.google.com directs traffic to 173.194.45.27 and 2607:f8b0:4004:c1f::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.
Both aspmx3.googlemail.com and alt2.aspmx.l.google.com resolve to 2a00:1450:400b:c02::1a IP addresses each.