vero.security - robtex.com
vero.security
security
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns0.centralnic.net ⭐ | ||||||
| NS | a.nic.security | ||||||
| NS | b.nic.security | ||||||
| NS | e.nic.security | ||||||
| NS | f.nic.security | ||||||
| SOA | ns0.centralnic.nethostmaster@centralnic.net serial=225756 | ||||||
Same first word
Similar names
DNS History
6 records (6 active, 0 former)
●NSns-1392.awsdns-46.org2026-06-10 → 2026-07-01 · 2 obs
● 2026-07-01 03:41:56
●NSns-141.awsdns-17.com2026-06-10 → 2026-07-01 · 2 obs
● 2026-07-01 03:41:56
●NSns-2040.awsdns-63.co.uk2026-06-10 → 2026-07-01 · 2 obs
● 2026-07-01 03:41:56
●NSns-552.awsdns-05.net2026-06-10 → 2026-07-01 · 2 obs
● 2026-07-01 03:41:56
●MXsmtp.google.com2026-06-10 → 2026-07-01 · 2 obs
● 2026-07-01 03:41:56
●A216.150.1.12026-06-10 → 2026-07-01 · 2 obs
● 2026-07-01 03:41:56
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| security | e.nic.security, f.nic.security, a.nic.security, b.nic.security | 8 records |
| vero.security | ns-141.awsdns-17.com, ns-2040.awsdns-63.co.uk, ns-1392.awsdns-46.org, ns-552.awsdns-05.net | - |
✅ Authoritative Response
Server:205.251.194.40
NS records: ns-141.awsdns-17.com, ns-2040.awsdns-63.co.uk, ns-1392.awsdns-46.org, ns-552.awsdns-05.net
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 683ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 216.150.1.1 |
| NS | 4 | ns-1392.awsdns-46.org, ns-141.awsdns-17.com... |
| MX | 1 | smtp.google.com (pri: 1) |
| TXT | 6 | MS=ms36259483, MS=ms55133499... |
| SOA | 1 | ns-141.awsdns-17.com awsdns-hostmaster.a |
📌 Glue Records Collected
Total: 8
In-bailiwick: 8 (a.nic.security, b.nic.security, e.nic.security...)
Analysis
IP Addresses
vero.security resolves to just one IP address, 216.150.1.1.
Two other host names, along with genegraph.eu, foldappdesktop.com and cebraarchitecture.dk, also share IP numbers with vero.security.
Name Servers
The NS records for vero.security point to four name servers: ns-141.awsdns-17.com, ns-552.awsdns-05.net, ns-1392.awsdns-46.org and ns-2040.awsdns-63.co.uk.
vero.security has at least partial name server overlap with other domains, such as d1md2ss18480pe.cloudfront.net, dev-cc.pe.directvgo.com, dreimann.net and two others.
ns-141.awsdns-17.com, ns-552.awsdns-05.net, ns-1392.awsdns-46.org and ns-2040.awsdns-63.co.uk all point to exactly two IP numbers each: ns-141.awsdns-17.com → 205.251.192.141 and 2600:9000:5300:8d00::1; ns-552.awsdns-05.net → 205.251.194.40 and 2600:9000:5302:2800::1; ns-1392.awsdns-46.org → 205.251.197.112 and 2600:9000:5305:7000::1; ns-2040.awsdns-63.co.uk → 205.251.199.248 and 2600:9000:5307:f800::1.
Mail Servers
The sole mail server for vero.security is smtp.google.com.
Among the domains sharing a mail server setup with vero.security are amaznet.com, neue.es, geomasoft.com and two others.
There is at least a partial MX overlap between vero.security and other domains, including wengerremodeling.com, m.org, neex.co.jp and two others.
alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and alt4.aspmx.l.google.com are mail servers that frequently appear together with these mail servers.
With 9 IP addresses total, smtp.google.com resolves to 172.253.62.26, 172.253.62.27, 172.253.115.26 and 6 others.