4wdtrips.net - robtex.com
4wdtrips.net
net
| 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=1785352907 | ||||||
Same first word
4wdtrips.net |
DNS History
15 records (7 active, 8 former)
○NSdns1.name-services.com2015-06-22 → 2017-04-20 · 4 obs
● 2017-04-20 02:06:06
○ 2026-04-02 00:33:04
○ 2026-07-29 19:49:06
●NSdns1.registrar-servers.com2026-04-02 → 2026-07-29 · 3 obs
● 2026-04-02 00:33:04
● 2026-07-29 19:49:06
○NSdns2.name-services.com2015-06-22 → 2017-04-20 · 4 obs
● 2017-04-20 02:06:06
○ 2026-04-02 00:33:04
○ 2026-07-29 19:49:06
●NSdns2.registrar-servers.com2026-04-02 → 2026-07-29 · 3 obs
● 2026-04-02 00:33:04
● 2026-07-29 19:49:06
○NSdns3.name-services.com2015-06-22 → 2017-04-20 · 4 obs
● 2017-04-20 02:06:06
○ 2026-04-02 00:33:04
○ 2026-07-29 19:49:06
○NSdns4.name-services.com2015-06-22 → 2017-04-20 · 4 obs
● 2017-04-20 02:06:06
○ 2026-04-02 00:33:04
○ 2026-07-29 19:49:06
○NSdns5.name-services.com2015-06-22 → 2017-04-20 · 4 obs
● 2017-04-20 02:06:06
○ 2026-04-02 00:33:04
○ 2026-07-29 19:49:06
●MXalt1.aspmx.l.google.com2015-06-22 → 2026-07-29 · 2 obs
● 2026-07-29 19:49:06
●MXalt2.aspmx.l.google.com2015-06-22 → 2026-07-29 · 2 obs
● 2026-07-29 19:49:06
●MXaspmx.l.google.com2015-06-22 → 2026-07-29 · 2 obs
● 2026-07-29 19:49:06
●MXaspmx2.googlemail.com2015-06-22 → 2026-07-29 · 2 obs
● 2026-07-29 19:49:06
●MXaspmx3.googlemail.com2015-06-22 → 2026-07-29 · 2 obs
● 2026-07-29 19:49:06
○A24.94.16.102017-04-20 → 2017-04-20 · 4 obs
● 2017-04-20 02:06:06
○ 2026-04-02 00:33:04
○ 2026-07-29 19:49:06
○A70.95.149.2112016-09-09 → 2016-09-09 · 4 obs
● 2016-09-09 15:09:18
○ 2017-04-20 02:06:06
○ 2026-07-29 19:49:06
○A99.111.98.2172015-06-22 → 2016-04-09 · 4 obs
● 2016-04-09 12:41:36
○ 2016-09-09 15:09:18
○ 2026-07-29 19:49:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | j.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, f.gtld-servers.net... | - |
| 4wdtrips.net | dns1.registrar-servers.com, dns2.registrar-servers.com | - |
✅ Authoritative Response
Server:156.154.132.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 4wdtrips.net (unsigned zone)
⏱️ Timing
Total: 351ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | dns1.registrar-servers.com, dns2.registrar-servers.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)... |
| SOA | 1 | dns1.registrar-servers.com hostmaster.re |
Analysis
Name Servers
4wdtrips.net has two authoritative name servers — dns1.registrar-servers.com and dns2.registrar-servers.com.
4wdtrips.net uses the same name servers as several other domains — among them igrinstitute.com, ursaplus.io, prachatham.com and two more.
The name servers for 4wdtrips.net are partially shared with other domains like patientcoroi.co, zioninsurance.com and emmonsco.com
These name servers tend to appear together with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
Both dns1.registrar-servers.com and dns2.registrar-servers.com have two IP addresses each. dns1.registrar-servers.com resolves to 156.154.132.200 and 2610:a1:1024::200; dns2.registrar-servers.com resolves to 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
4wdtrips.net is handled by five mail servers: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
4wdtrips.net has at least partial mail server overlap with other domains such as ns500693.ns500693.ns500693.ns500693.ns500693.ns500699.ns500693.ns500588.ns500699.ns500699.ns500588.ns500699.ns500602.dtrkdll.com, ns500742.ns500754.ns500731.ns500731.ns500671.ns500704.ns500671.ns500731.ns500671.ns500688.ns500291.ns500678.ns500649.ns500649.ns500666.ns500142.lusty(0x736c7574)z.com, ns500754.ns500742.ns500754.ns500754.ns500731.ns500671.ns500704.ns500671.ns500671.ns500649.ns500666.ns500291.ns500131.lustychickser.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
aspmx3.googlemail.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
aspmx.l.google.com resolves to 64.233.180.26 and 2607:f8b0:4004:c2d::1a.
alt1.aspmx.l.google.com resolves to 108.177.123.27 and 2800:3f0:4003:c0f::1b.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1a.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 2800:3f0:4003:c0f::1b IP addresses.
The host names aspmx2.googlemail.com and alt1.aspmx.l.google.com both resolve to 108.177.123.27 IP addresses.
The host names aspmx3.googlemail.com and alt2.aspmx.l.google.com both resolve to 172.253.116.26 IP addresses.