riangle.com - dns.ninja
riangle.com
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=1783214366 | ||||||
Same first word
riangle.com |
Similar names
DNS History
15 records (8 active, 7 former)
○NSdns.site5.com2015-07-25 → 2016-04-08 · 4 obs
● 2016-04-08 18:43:38
○ 2017-03-30 15:52:06
○ 2026-07-05 01:38:00
○NSdns2.site5.com2015-07-25 → 2016-04-08 · 4 obs
● 2016-04-08 18:43:38
○ 2017-03-30 15:52:06
○ 2026-07-05 01:38:00
●NSliz.ns.cloudflare.com2017-03-30 → 2026-07-05 · 3 obs
● 2017-03-30 15:52:06
● 2026-07-05 01:38:00
●NSpete.ns.cloudflare.com2017-03-30 → 2026-07-05 · 3 obs
● 2017-03-30 15:52:06
● 2026-07-05 01:38:00
●MXalt1.aspmx.l.google.com2017-03-30 → 2026-07-05 · 2 obs
● 2026-07-05 01:38:00
●MXalt2.aspmx.l.google.com2017-03-30 → 2026-07-05 · 2 obs
● 2026-07-05 01:38:00
●MXalt3.aspmx.l.google.com2017-03-30 → 2026-07-05 · 2 obs
● 2026-07-05 01:38:00
●MXalt4.aspmx.l.google.com2017-03-30 → 2026-07-05 · 2 obs
● 2026-07-05 01:38:00
●MXaspmx.l.google.com2017-03-30 → 2026-07-05 · 2 obs
● 2026-07-05 01:38:00
○A104.27.156.1302017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 15:52:06
○ 2026-02-15 14:31:26
○ 2026-07-05 01:38:00
○A104.27.157.1302017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 15:52:06
○ 2026-02-15 14:31:26
○ 2026-07-05 01:38:00
○A174.120.146.1462015-07-25 → 2016-04-08 · 4 obs
● 2016-04-08 18:43:38
○ 2017-03-30 15:52:06
○ 2026-07-05 01:38:00
○A2400:cb00:2048:1::681b:9c822017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 15:52:06
○ 2026-02-15 14:31:26
○ 2026-07-05 01:38:00
○A2400:cb00:2048:1::681b:9d822017-03-30 → 2017-03-30 · 4 obs
● 2017-03-30 15:52:06
○ 2026-02-15 14:31:26
○ 2026-07-05 01:38:00
●A76.76.21.212026-02-15 → 2026-07-05 · 3 obs
● 2026-02-15 14:31:26
● 2026-07-05 01:38:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| riangle.com | pete.ns.cloudflare.com, liz.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.136
NS records: pete.ns.cloudflare.com, liz.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for riangle.com (unsigned zone)
⏱️ Timing
Total: 192ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 76.76.21.21 |
| NS | 2 | liz.ns.cloudflare.com, pete.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | google-site-verification=k2EeHE3p-S2g5FB |
| SOA | 1 | liz.ns.cloudflare.com dns.cloudflare.com |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (pete.ns.cloudflare.com, pete.ns.cloudflare.com, pete.ns.cloudflare.com...)
Analysis
IP Addresses
riangle.com resolves to one IP address: 76.76.21.21.
placed.us, epicstart.ai, cyber-slacker.com and two other host names share IP numbers with riangle.com.
Name Servers
riangle.com has two authoritative name servers — liz.ns.cloudflare.com and pete.ns.cloudflare.com.
riangle.com uses the same name servers as several other domains — among them accad.org, inform.kz, vivis.me and two more.
There is at least partial name server overlap between riangle.com and other domains — peplus.lk, careeradvisorvantage.qpon, skuap.com and two more among them.
These name servers are routinely deployed together with the name servers jason.ns.cloudflare.com.
Hostnames that resolve to 6 IP addresses:
liz.ns.cloudflare.com points to 108.162.192.189, 172.64.32.189, 173.245.58.189 and 3 other IP addresses.
pete.ns.cloudflare.com points to 108.162.193.136, 172.64.33.136, 173.245.59.136 and 3 other IP addresses.
Mail Servers
Five mail servers handle riangle.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
riangle.com has at least partial mail server overlap with other domains such as ns500734.ns500699.ns500693.ns500699.ns500734.ns500693.ns500734.ns500728.ns500588.ns500588.ns500693.ns500588.ns500588.ns500588.ns500588.ns500588.dtrkdll.com, ns500698.ns500758.ns500759.ns500759.ns500698.ns500735.ns500735.ns500698.ns500576.ns500698.ns500576.ns500708.ns500698.ns500619.ns500652.ns500576.trackreceptor.com, ns500599.ns500599.ns500737.ns500724.ns500737.ns500724.ns500724.ns500724.ns500697.ns500697.ns500697.ns500599.yummyflingsfinder.com and two more.
The mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com are commonly seen alongside these mail servers.
Hostnames that resolve to two IP addresses:
aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c1b::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1a.
alt4.aspmx.l.google.com resolves to 172.253.157.26 and 2a00:1450:400c:c23::1b.