fdgtech.com - dns.ninja
fdgtech.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=1786250304 | ||||||
Same first word
fdgtech.com |
DNS History
9 records (8 active, 1 former)
●NSns39.domaincontrol.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
●NSns40.domaincontrol.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
●MXalt1.aspmx.l.google.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
●MXalt2.aspmx.l.google.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
●MXaspmx.l.google.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
●MXaspmx2.googlemail.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
●MXaspmx3.googlemail.com2016-12-16 → 2026-08-09 · 2 obs
● 2026-08-09 05:04:00
○A107.180.0.2312016-12-16 → 2017-10-29 · 4 obs
● 2017-10-29 18:45:50
○ 2026-03-01 00:40:46
○ 2026-08-09 05:04:00
●A107.180.118.2432026-03-01 → 2026-08-09 · 3 obs
● 2026-03-01 00:40:46
● 2026-08-09 05:04:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | j.gtld-servers.net, h.gtld-servers.net, f.gtld-servers.net, d.gtld-servers.net... | - |
| fdgtech.com | ns39.domaincontrol.com, ns40.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:173.201.77.20
NS records: ns39.domaincontrol.com, ns40.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fdgtech.com (unsigned zone)
⏱️ Timing
Total: 193ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 107.180.118.243 |
| NS | 2 | ns39.domaincontrol.com, ns40.domaincontrol.com |
| MX | 5 | alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns39.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns39.domaincontrol.com, ns39.domaincontrol.com, ns40.domaincontrol.com...)
Analysis
IP Addresses
fdgtech.com points to a single IP number: 107.180.118.243.
Additional host names — mail.srmaterial.com, msmgi.com, oceanstarltd.com and two others — share IP numbers with fdgtech.com.
Name Servers
fdgtech.com is delegated to two name servers: ns39.domaincontrol.com and ns40.domaincontrol.com.
fdgtech.com shares its name server setup with other domains, including tag-ease.com, akashseeds.com, agaloc.com and two others.
ns39.domaincontrol.com and ns40.domaincontrol.com each resolve to two IP addresses: ns39.domaincontrol.com points to 97.74.109.20 and 2603:5:21d1::14, while ns40.domaincontrol.com points to 173.201.77.20 and 2603:5:22d1::14.
Mail Servers
fdgtech.com is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
fdgtech.com shares mail servers — at least in part — with other domains, including comune.bo.it, eastcorkoutdooradventures.org, embeddeddatasystems.com and two others.
These mail servers are frequently used alongside mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 other.
Host names with two IP numbers:
aspmx2.googlemail.com points to 192.178.234.26 and 2800:3f0:4003:c14::1a.
aspmx3.googlemail.com points to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com points to 142.251.179.26 and 2607:f8b0:4004:c25::1b.
alt1.aspmx.l.google.com points to 192.178.234.27 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com points to 172.253.116.27 and 2a00:1450:400b:c02::1b.
aspmx2.googlemail.com and alt1.aspmx.l.google.com are host names that each point to 2800:3f0:4003:c14::1a IP addresses.
aspmx3.googlemail.com and alt2.aspmx.l.google.com are host names that each point to 2a00:1450:400b:c02::1b IP addresses.