intercom.cloud - dns.ninja
intercom.cloud
cloud
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1780560030 | ||||||
Same first word
Similar names
DNS History
9 records (9 active, 0 former)
●NSns-1531.awsdns-63.org2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●NSns-1761.awsdns-28.co.uk2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●NSns-247.awsdns-30.com2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●NSns-570.awsdns-07.net2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●MXalt1.aspmx.l.google.com2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●MXalt2.aspmx.l.google.com2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●MXalt3.aspmx.l.google.com2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●MXalt4.aspmx.l.google.com2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
●MXaspmx.l.google.com2026-02-19 → 2026-06-04 · 2 obs
● 2026-06-04 08:20:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cloud | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| intercom.cloud | ns-247.awsdns-30.com, ns-570.awsdns-07.net, ns-1531.awsdns-63.org, ns-1761.awsdns-28.co.uk | - |
✅ Authoritative Response
Server:205.251.198.225
NS records: ns-247.awsdns-30.com, ns-570.awsdns-07.net, ns-1531.awsdns-63.org, ns-1761.awsdns-28.co.uk
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for intercom.cloud (unsigned zone)
⏱️ Timing
Total: 609ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1531.awsdns-63.org, ns-1761.awsdns-28.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | MS=ms60564126, v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-1761.awsdns-28.co.uk awsdns-hostmaste |
Analysis
Name Servers
intercom.cloud is served by 4 authoritative name servers: ns-247.awsdns-30.com, ns-570.awsdns-07.net, ns-1531.awsdns-63.org and ns-1761.awsdns-28.co.uk.
intercom.cloud has at least partial name server overlap with other domains, such as d32h65j3m1jqfb.cloudfront.net, na.mobilemesk.skill.music.a2z.com, lemidi-yokohama.com and two others.
ns-247.awsdns-30.com, ns-570.awsdns-07.net, ns-1531.awsdns-63.org and ns-1761.awsdns-28.co.uk all point to exactly two IP numbers each: ns-247.awsdns-30.com → 205.251.192.247 and 2600:9000:5300:f700::1; ns-570.awsdns-07.net → 205.251.194.58 and 2600:9000:5302:3a00::1; ns-1531.awsdns-63.org → 205.251.197.251 and 2600:9000:5305:fb00::1; ns-1761.awsdns-28.co.uk → 205.251.198.225 and 2600:9000:5306:e100::1.
Mail Servers
The MX records for intercom.cloud point to 5 mail servers: 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 intercom.cloud and other domains, including ppf.cool, shopfans.io, ajduenas.com and two others.
These mail servers frequently co-occur with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and two others.
Host names that have two IP addresses:
aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1b.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 173.194.76.27 and 2a00:1450:400c:c00::1a.
Both aspmx.l.google.com and alt3.aspmx.l.google.com resolve to 2a00:1450:4009:c0f::1b IP addresses each.