trendytailwagger.com - robtex.com
trendytailwagger.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=1776093567 | ||||||
Same first word
trendytailwagger.com |
DNS History
12 records (12 active, 0 former)
βNSdns018.c.register.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βNSdns060.b.register.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βNSdns083.d.register.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βNSdns1.register.com2026-04-13 β 2026-04-13 Β· 3 obs
β 2026-04-13 15:45:28
β 2026-04-13 15:45:30
βNSdns178.a.register.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βNSdns2.register.com2026-04-13 β 2026-04-13 Β· 3 obs
β 2026-04-13 15:45:28
β 2026-04-13 15:45:30
βMXalt1.aspmx.l.google.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βMXalt2.aspmx.l.google.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βMXalt3.aspmx.l.google.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βMXalt4.aspmx.l.google.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βMXaspmx.l.google.com2020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
βA199.34.228.662020-03-18 β 2026-04-13 Β· 2 obs
β 2026-04-13 15:45:30
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| trendytailwagger.com | dns1.register.com, dns2.register.com | 2 records |
β Authoritative Response
Server:162.159.26.197
NS records: dns1.register.com, dns2.register.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for trendytailwagger.com (unsigned zone)
β±οΈ Timing
Total: 173ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 199.34.228.66 |
| NS | 4 | dns018.c.register.com, dns083.d.register.com... |
| MX | 5 | alt4.aspmx.l.google.com (pri: 10), aspmx.l.google.com (pri: 1)... |
| SOA | 1 | dns178.a.register.com root.register.com |
π Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (dns1.register.com, dns2.register.com)
Analysis
IP Addresses
trendytailwagger.com points to a single IP: 199.34.228.66.
Other host names, for instance drjohnchar.com, roboticsuwm.com, mypeaceup.com, manitoulinstreams.com and kntogroup.com share IP numbers with trendytailwagger.com.
Name Servers
trendytailwagger.com is delegated to six name servers: dns1.register.com, dns2.register.com, dns178.a.register.com, dns060.b.register.com, dns018.c.register.com and dns083.d.register.com.
trendytailwagger.com at least partially shares its name servers with other domains, for instance waysvilleengineering.com, tygard2000.us, sandypawsmv.com, johnscarvings.com and bumper2bumpercustoms.com.
These name servers are commonly used with dns177.d.register.com, dns082.d.register.com, dns176.d.register.com, dns010.d.register.com, dns1.srsplus.com, dns2.srsplus.com, dns027.c.register.com, dns011.c.register.com, dns023.c.register.com and dns022.c.register.com.
Host names with one IP number:
The host name dns1.register.com maps to 162.159.27.248.
The host name dns2.register.com maps to 162.159.26.197.
The host name dns178.a.register.com maps to 216.21.231.178.
The host name dns060.b.register.com maps to 216.21.232.60.
The host name dns018.c.register.com maps to 216.21.235.18.
The host name dns083.d.register.com maps to 216.21.236.83.
Mail Servers
Five mail servers handle trendytailwagger.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com.
trendytailwagger.com shares some mail servers with other domains, including qtvsports.com, ns500734.ns500734.ns500699.ns500693.ns500699.ns500693.ns500693.ns500693.ns500588.ns500693.ns500693.ns500612.ns500588.ns500602.ns500578.ns500110.dtrkdll.com, ns500754.ns500742.ns500731.ns500754.ns500731.ns500742.ns500671.ns500688.ns500671.ns500649.ns500649.ns500671.lusty(0x736c7574)z.com, ns500742.ns500742.ns500754.ns500731.ns500671.ns500671.ns500704.ns500671.ns500649.ns500678.ns500666.ns500142.lusty(0x736c7574)z.com and ns500754.ns500671.ns500754.ns500742.ns500742.ns500742.ns500731.ns500704.ns500688.ns500688.ns500671.ns500704.ns500678.ns500678.ns500688.ns500671.ns500649.lustychickser.com.
these mail servers are often used alongside the mail servers aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com and aspmx5.googlemail.com.
Host names with two IP numbers:
aspmx.l.google.com points to 2607:f8b0:4004:c21::1b and 172.253.63.27.
alt1.aspmx.l.google.com points to 2800:3f0:4003:c0f::1b and 108.177.123.26.
alt2.aspmx.l.google.com points to 2607:f8b0:4023:1015::1a and 172.253.135.26.
alt3.aspmx.l.google.com points to 2a00:1450:4001:c21::1b and 142.251.127.27.
alt4.aspmx.l.google.com points to 2a00:1450:4025:c01::1b and 142.250.147.26.