fledgeconnect.com - dns.ninja
fledgeconnect.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=1785907539 | ||||||
Same first word
fledgeconnect.com |
DNS History
14 records (10 active, 4 former)
●NSns-1115.awsdns-11.org2017-12-22 → 2026-08-05 · 3 obs
● 2017-12-22 06:00:08
● 2026-08-05 05:53:24
●NSns-1584.awsdns-06.co.uk2017-12-22 → 2026-08-05 · 3 obs
● 2017-12-22 06:00:08
● 2026-08-05 05:53:24
●NSns-253.awsdns-31.com2017-12-22 → 2026-08-05 · 3 obs
● 2017-12-22 06:00:08
● 2026-08-05 05:53:24
●NSns-803.awsdns-36.net2017-12-22 → 2026-08-05 · 3 obs
● 2017-12-22 06:00:08
● 2026-08-05 05:53:24
○NSns37.domaincontrol.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-12-22 06:00:08
○ 2026-08-05 05:53:24
○NSns38.domaincontrol.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-12-22 06:00:08
○ 2026-08-05 05:53:24
●MXalt1.aspmx.l.google.com2016-12-15 → 2026-08-05 · 2 obs
● 2026-08-05 05:53:24
●MXalt2.aspmx.l.google.com2016-12-15 → 2026-08-05 · 2 obs
● 2026-08-05 05:53:24
●MXalt3.aspmx.l.google.com2016-12-15 → 2026-08-05 · 2 obs
● 2026-08-05 05:53:24
●MXalt4.aspmx.l.google.com2016-12-15 → 2026-08-05 · 2 obs
● 2026-08-05 05:53:24
●MXaspmx.l.google.com2016-12-15 → 2026-08-05 · 2 obs
● 2026-08-05 05:53:24
○A107.180.48.872016-12-15 → 2016-12-15 · 3 obs
○ 2017-12-22 06:00:08
○ 2026-08-05 05:53:24
●A3.131.36.1252026-04-06 → 2026-08-05 · 3 obs
● 2026-04-06 16:02:18
● 2026-08-05 05:53:24
○A52.15.111.02017-12-22 → 2017-12-22 · 4 obs
● 2017-12-22 06:00:08
○ 2026-04-06 16:02:18
○ 2026-08-05 05:53:24
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net... | - |
| fledgeconnect.com | ns-253.awsdns-31.com, ns-803.awsdns-36.net, ns-1584.awsdns-06.co.uk, ns-1115.awsdns-11.org | 2 records |
✅ Authoritative Response
Server:205.251.192.253
NS records: ns-253.awsdns-31.com, ns-803.awsdns-36.net, ns-1584.awsdns-06.co.uk, ns-1115.awsdns-11.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fledgeconnect.com (unsigned zone)
⏱️ Timing
Total: 438ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 3.131.36.125 |
| NS | 4 | ns-1115.awsdns-11.org, ns-1584.awsdns-06.co.uk... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:servers.mcsv.net ?all |
| SOA | 1 | ns-253.awsdns-31.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-253.awsdns-31.com, ns-253.awsdns-31.com)
Analysis
IP Addresses
fledgeconnect.com directs to one IP number, which is 3.131.36.125.
Host names like ec2-3-131-36-125.us-east-2.compute.amazonaws.com are further examples that share IP numbers with fledgeconnect.com.
Name Servers
The domain fledgeconnect.com is delegated to these four name servers: ns-253.awsdns-31.com, ns-803.awsdns-36.net, ns-1115.awsdns-11.org and ns-1584.awsdns-06.co.uk.
There is at least partial name server overlap between fledgeconnect.com and other domains — expertmarket.com, tracking.dpgmedia.cloud, gz-aneje.biz and two more among them.
All four hostnames — ns-253.awsdns-31.com, ns-803.awsdns-36.net, ns-1115.awsdns-11.org and ns-1584.awsdns-06.co.uk — resolve to two IP numbers apiece: ns-253.awsdns-31.com to 205.251.192.253 and 2600:9000:5300:fd00::1; ns-803.awsdns-36.net to 205.251.195.35 and 2600:9000:5303:2300::1; ns-1115.awsdns-11.org to 205.251.196.91 and 2600:9000:5304:5b00::1; ns-1584.awsdns-06.co.uk to 205.251.198.48 and 2600:9000:5306:3000::1.
Mail Servers
fledgeconnect.com has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
fledgeconnect.com shares at least some of its mail servers with other domains — for example ns500759.ns500758.ns500759.ns500759.ns500736.ns500698.ns500736.ns500735.ns500735.ns500698.ns500736.ns500698.ns500708.ns500698.ns500619.ns500619.ns500619.trackreceptor.com, ns500758.ns500759.ns500698.ns500758.ns500735.ns500698.ns500576.ns500698.ns500698.ns500708.ns500619.ns500698.ns500652.ns500576.trackreceptor.com, ns500734.ns500693.ns500734.ns500699.ns500699.ns500693.ns500734.ns500588.ns500699.ns500699.ns500612.ns500632.ns500588.ns500588.ns500588.dtrkdll.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to two addresses: 142.251.111.26 and 2607:f8b0:4004:c09::1a.
alt1.aspmx.l.google.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1b.