fdserv.com - dns.ninja
fdserv.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=1785292322 | ||||||
Subdomains
mx.fdserv.com |
Same first word
fdserv.com |
Similar names
fedvrs.us |
fredsv.com |
sfrdev.fr |
dsferv.bar |
dfserv.de |
fedsrv.com |
drvsef.com |
dfserv.com |
fredvs.github.io |
rfsdev.com |
revfds.com |
rfsdev.net |
dfsver.click |
DNS History
13 records (9 active, 4 former)
●NSns1.verio.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
○NSns13.ixwebhosting.com2015-08-15 → 2018-07-22 · 4 obs
● 2018-07-22 00:15:34
○ 2026-07-08 02:16:22
○ 2026-07-29 02:37:36
○NSns14.ixwebhosting.com2015-08-15 → 2018-07-22 · 4 obs
● 2018-07-22 00:15:34
○ 2026-07-08 02:16:22
○ 2026-07-29 02:37:36
●NSns2.verio.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
●MXalt1.aspmx.l.google.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
●MXalt2.aspmx.l.google.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
●MXalt3.aspmx.l.google.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
●MXalt4.aspmx.l.google.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
●MXaspmx.l.google.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
○MXmail406.ixwebhosting.com2015-08-15 → 2018-07-22 · 4 obs
● 2018-07-22 00:15:34
○ 2026-07-08 02:16:22
○ 2026-07-29 02:37:36
●MXmx.fdserv.com2026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
●A66.96.146.1292026-07-08 → 2026-07-29 · 3 obs
● 2026-07-08 02:16:22
● 2026-07-29 02:37:36
○A98.130.118.492015-08-15 → 2018-07-22 · 4 obs
● 2018-07-22 00:15:34
○ 2026-07-08 02:16:22
○ 2026-07-29 02:37:36
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, d.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net... | - |
| fdserv.com | ns1.verio.com, ns2.verio.com | 2 records |
✅ Authoritative Response
Server:162.159.25.208
NS records: ns1.verio.com, ns2.verio.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for fdserv.com (unsigned zone)
⏱️ Timing
Total: 1719ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.96.146.129 |
| NS | 2 | ns1.verio.com, ns2.verio.com |
| MX | 6 | ALT3.ASPMX.L.GOOGLE.com (pri: 10), ALT4.ASPMX.L.GOOGLE.com (pri: 10)... |
| TXT | 1 | v=spf1 ip4:66.96.128.0/18 include:websit |
| SOA | 1 | ns1.verio.com dnsadmin.verio.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.verio.com, ns2.verio.com)
Analysis
Hierarchy
mx.fdserv.com is delegated beneath fdserv.com.
IP Addresses
fdserv.com has exactly one IP address — 66.96.146.129.
nebraskagasturbine.com, www.toxcor-associates.com, mail.stratfordbrakettes.com plus two other host names have IP numbers in common with fdserv.com.
Name Servers
fdserv.com uses two name servers for its delegation: ns1.verio.com and ns2.verio.com.
The name server configuration of fdserv.com is shared with other domains, for instance megaroller.net, japaneseswordcalendar.org, bci-newark.org and two others.
There is at least partial name server overlap between fdserv.com and other domains — thoughtbunny.org, astralinfo.org, tmcorp.us and two more among them.
These name servers frequently co-occur with the name servers ns1.yourhostingaccount.com and ns2.yourhostingaccount.com.
ns1.verio.com → 162.159.24.252 and ns2.verio.com → 162.159.25.208: one IP number per host name.
Mail Servers
fdserv.com accepts email via 6 mail servers: mx.fdserv.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.
At least some of the mail servers used by fdserv.com are shared with other domains: ns500759.ns500758.ns500758.ns500698.ns500736.ns500698.ns500735.ns500576.ns500576.ns500708.ns500576.ns500686.ns500619.trackreceptor.com, ns500758.ns500758.ns500759.ns500758.ns500736.ns500698.ns500736.ns500736.ns500735.ns500576.ns500708.ns500698.ns500698.ns500619.ns500576.trackreceptor.com, ns500599.ns500599.ns500724.ns500737.ns500599.ns500737.ns500583.ns500697.ns500682.ns500599.yummyflingsfinder.com and two others among them.
These mail servers are often deployed together with alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 other mail servers.
Host names pointing to two IP addresses:
mx.fdserv.com directs traffic to 66.96.140.158 and 66.96.140.159.
aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c08::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1a.
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 172.253.157.26 and 2a00:1450:400c:c23::1a.