beaconlinkpro.com - dns.ninja
beaconlinkpro.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=1785247917 | ||||||
Same first word
beaconlinkpro.com |
DNS History
10 records (10 active, 0 former)
●NSns-1511.awsdns-60.org2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●NSns-1716.awsdns-22.co.uk2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●NSns-390.awsdns-48.com2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●NSns-878.awsdns-45.net2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●MXalt1.aspmx.l.google.com2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●MXalt2.aspmx.l.google.com2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●MXalt3.aspmx.l.google.com2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●MXalt4.aspmx.l.google.com2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●MXaspmx.l.google.com2026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
●A3.134.155.2252026-03-19 → 2026-07-28 · 2 obs
● 2026-07-28 14:14:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| beaconlinkpro.com | ns-390.awsdns-48.com, ns-878.awsdns-45.net, ns-1716.awsdns-22.co.uk, ns-1511.awsdns-60.org | 2 records |
✅ Authoritative Response
Server:205.251.195.110
NS records: ns-390.awsdns-48.com, ns-878.awsdns-45.net, ns-1716.awsdns-22.co.uk, ns-1511.awsdns-60.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for beaconlinkpro.com (unsigned zone)
⏱️ Timing
Total: 395ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.134.155.225 |
| NS | 4 | ns-1511.awsdns-60.org, ns-1716.awsdns-22.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 ip4:3.134.155.225 ip4:3.14.90.206 |
| SOA | 1 | ns-1716.awsdns-22.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-390.awsdns-48.com, ns-390.awsdns-48.com)
Analysis
IP Addresses
beaconlinkpro.com resolves to just one IP address, 3.134.155.225.
Other host names share IP numbers with beaconlinkpro.com; ec2-3-134-155-225.us-east-2.compute.amazonaws.com is one such example.
Name Servers
The NS records for beaconlinkpro.com point to four name servers: ns-390.awsdns-48.com, ns-878.awsdns-45.net, ns-1511.awsdns-60.org and ns-1716.awsdns-22.co.uk.
beaconlinkpro.com shares at least some of its name servers with other domains, including 134.224.3.in-addr.arpa, 12.174.35.in-addr.arpa, 67.25.100.in-addr.arpa and two others.
These name servers are frequently seen alongside ns1-24-us-east-1.ec2-rdns.amazonaws.com, ns2-24-us-east-1.ec2-rdns.amazonaws.com, ns3-24-us-east-1.ec2-rdns.amazonaws.com and 4 other name servers.
The host names ns-390.awsdns-48.com, ns-878.awsdns-45.net, ns-1511.awsdns-60.org and ns-1716.awsdns-22.co.uk each resolve to two IP addresses: ns-390.awsdns-48.com resolves to 205.251.193.134 and 2600:9000:5301:8600::1; ns-878.awsdns-45.net resolves to 205.251.195.110 and 2600:9000:5303:6e00::1; ns-1511.awsdns-60.org resolves to 205.251.197.231 and 2600:9000:5305:e700::1; ns-1716.awsdns-22.co.uk resolves to 205.251.198.180 and 2600:9000:5306:b400::1.
Mail Servers
Mail for beaconlinkpro.com is handled by five mail servers, namely 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 beaconlinkpro.com and other domains, including credemlab.com, sprinter.io, ns500768.ns500759.ns500759.ns500698.ns500758.ns500758.ns500735.ns500698.ns500735.ns500736.ns500735.ns500576.ns500576.ns500576.ns500708.ns500652.trackreceptor.com and two others.
These mail servers tend to appear in combination with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.
Host names that have two IP addresses:
aspmx.l.google.com maps to two IP addresses — 142.251.179.26 and 2607:f8b0:4004:c23::1b.
alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.26 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::1b.
alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.26 and 2a00:1450:400c:c23::1a.