vcrowd.com - dns.ninja
vcrowd.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=1781440840 | ||||||
Same first word
Similar names
DNS History
17 records (7 active, 10 former)
●NSdns1.registrar-servers.com2026-03-01 → 2026-06-14 · 3 obs
● 2026-03-01 18:39:26
● 2026-06-14 13:00:18
●NSdns2.registrar-servers.com2026-03-01 → 2026-06-14 · 3 obs
● 2026-03-01 18:39:26
● 2026-06-14 13:00:18
○NSns1.netregistry.net2017-02-08 → 2020-01-17 · 5 obs
● 2017-02-08 19:31:26
● 2020-01-17 04:03:26
○ 2026-03-01 18:39:26
○ 2026-06-14 13:00:18
○NSns1.pipedns.com2015-07-10 → 2016-05-02 · 4 obs
● 2016-05-02 10:15:08
○ 2017-02-08 19:31:26
○ 2026-06-14 13:00:18
○NSns2.netregistry.net2017-02-08 → 2020-01-17 · 5 obs
● 2017-02-08 19:31:26
● 2020-01-17 04:03:26
○ 2026-03-01 18:39:26
○ 2026-06-14 13:00:18
○NSns2.pipedns.com2015-07-10 → 2016-05-02 · 4 obs
● 2016-05-02 10:15:08
○ 2017-02-08 19:31:26
○ 2026-06-14 13:00:18
○NSns3.netregistry.net2017-02-08 → 2020-01-17 · 5 obs
● 2017-02-08 19:31:26
● 2020-01-17 04:03:26
○ 2026-03-01 18:39:26
○ 2026-06-14 13:00:18
○NSns3.pipedns.com2015-07-10 → 2016-05-02 · 4 obs
● 2016-05-02 10:15:08
○ 2017-02-08 19:31:26
○ 2026-06-14 13:00:18
●MXalt1.aspmx.l.google.com2015-07-10 → 2026-06-14 · 2 obs
● 2026-06-14 13:00:18
●MXalt2.aspmx.l.google.com2015-07-10 → 2026-06-14 · 2 obs
● 2026-06-14 13:00:18
●MXaspmx.l.google.com2015-07-10 → 2026-06-14 · 2 obs
● 2026-06-14 13:00:18
●MXaspmx2.googlemail.com2015-07-10 → 2026-06-14 · 2 obs
● 2026-06-14 13:00:18
●MXaspmx3.googlemail.com2015-07-10 → 2026-06-14 · 2 obs
● 2026-06-14 13:00:18
○MXaspmx4.googlemail.com2015-07-10 → 2020-01-17 · 4 obs
● 2020-01-17 04:03:26
○ 2026-03-01 18:39:26
○ 2026-06-14 13:00:18
○MXaspmx5.googlemail.com2015-07-10 → 2020-01-17 · 4 obs
● 2020-01-17 04:03:26
○ 2026-03-01 18:39:26
○ 2026-06-14 13:00:18
○A173.254.28.812015-07-10 → 2016-05-02 · 4 obs
● 2016-05-02 10:15:08
○ 2017-02-08 19:31:26
○ 2026-06-14 13:00:18
○A54.253.120.792017-02-08 → 2020-01-17 · 5 obs
● 2017-02-08 19:31:26
● 2020-01-17 04:03:26
○ 2026-03-01 18:39:26
○ 2026-06-14 13:00:18
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, c.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net... | - |
| vcrowd.com | dns1.registrar-servers.com, dns2.registrar-servers.com | 4 records |
✅ Authoritative Response
Server:156.154.133.200
NS records: dns1.registrar-servers.com, dns2.registrar-servers.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for vcrowd.com (unsigned zone)
⏱️ Timing
Total: 220ms | 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 |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (dns1.registrar-servers.com, dns1.registrar-servers.com, dns2.registrar-servers.com...)
Analysis
Name Servers
vcrowd.com uses two name servers for its delegation: dns1.registrar-servers.com and dns2.registrar-servers.com.
vcrowd.com uses the same name servers as several other domains — among them jamespfeffer.com, loktoto.com, tedkato.com and two more.
vcrowd.com partially shares its NS delegation with several other domains, including rkesports.com, waterjetgarnet.co.uk, onoko.org and two others.
These name servers regularly co-occur with the name servers dns3.registrar-servers.com, dns4.registrar-servers.com and dns5.registrar-servers.com.
The two host names dns1.registrar-servers.com and dns2.registrar-servers.com each have a pair of IP addresses: dns1.registrar-servers.com has 156.154.132.200 and 2610:a1:1024::200, and dns2.registrar-servers.com has 156.154.133.200 and 2610:a1:1025::200.
Mail Servers
Mail for vcrowd.com is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.
vcrowd.com has at least partial mail server overlap with other domains such as ns500821.ns500794.ns500795.ns500794.ns500821.ns500821.ns500794.ns500794.ns500795.ns500790.ns500795.lustypartnersfinder.com, botverse.com, opticalcentresandton.com and two more.
These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt4.aspmx.l.google.com and 3 others.
Hostnames that resolve to two IP addresses:
aspmx2.googlemail.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
aspmx3.googlemail.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1a.
aspmx.l.google.com directs traffic to 172.253.115.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1a IP addresses each.
Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.27 IP addresses each.