vaap.com - robtex.com

vaap.com

DNSSEC⚠️ Not signed
NSns1.domainrecover.com ⚠️ Not in zone NS records
A149.248.38.58πŸ‡ΊπŸ‡Έ AS-VULTR149.248.32.0/20 Vultr Assigned Prefix
PTR149.248.38.58.vultrusercontent.com
NSns2.domainrecover.com ⚠️ Not in zone NS records
A199.247.16.62πŸ‡©πŸ‡ͺ AS-VULTR199.247.16.0/21 Vultr Assigned Prefix
PTR199.247.16.62.vultrusercontent.com

com

Same first word

Similar names

DNS History

11 records (2 active, 9 former)

20162017201820192020202120222023202420252026NSns1.domainrecover.comns2.domainrecover.comhost.tradenames.comns.tradenames.comMXmxs1.tradenames.commxs2.tradenames.comA141.8.230.2066.45.246.14067.209.228.107CNAMEpres.serverhome.comsnews.serverhome.com
β—‹NShost.tradenames.com2015-11-06 β†’ 2016-04-02 Β· 4 obs
● 2015-11-06 13:20:40
● 2016-04-02 09:24:30
β—‹ 2017-04-03 21:07:40
β—‹ 2026-07-26 10:31:54
β—‹NSns.tradenames.com2015-11-06 β†’ 2016-04-02 Β· 4 obs
● 2015-11-06 13:20:40
● 2016-04-02 09:24:30
β—‹ 2017-04-03 21:07:40
β—‹ 2026-07-26 10:31:54
●NSns1.domainrecover.com2026-07-02 β†’ 2026-07-26 Β· 3 obs
β—‹ 2017-04-03 21:07:40
● 2026-07-02 12:50:00
● 2026-07-26 10:31:54
●NSns2.domainrecover.com2026-07-02 β†’ 2026-07-26 Β· 3 obs
β—‹ 2017-04-03 21:07:40
● 2026-07-02 12:50:00
● 2026-07-26 10:31:54
β—‹MXmxs1.tradenames.com2015-07-10 β†’ 2016-04-02 Β· 4 obs
● 2015-07-10 04:22:50
● 2016-04-02 09:24:30
β—‹ 2017-04-03 21:07:40
β—‹ 2026-07-26 10:31:54
β—‹MXmxs2.tradenames.com2015-07-10 β†’ 2016-04-02 Β· 4 obs
● 2015-07-10 04:22:50
● 2016-04-02 09:24:30
β—‹ 2017-04-03 21:07:40
β—‹ 2026-07-26 10:31:54
β—‹A141.8.230.202017-04-03 β†’ 2017-05-07 Β· 5 obs
β—‹ 2016-04-02 09:24:30
● 2017-04-03 21:07:40
● 2017-05-07 16:58:28
β—‹ 2020-04-23 18:58:00
β—‹ 2026-07-26 10:31:54
β—‹A66.45.246.1402015-11-06 β†’ 2016-04-02 Β· 5 obs
β—‹ 2015-07-10 04:22:50
● 2015-11-06 13:20:40
● 2016-04-02 09:24:30
β—‹ 2017-04-03 21:07:40
β—‹ 2026-07-26 10:31:54
β—‹A67.209.228.1072015-07-10 β†’ 2015-07-10 Β· 3 obs
● 2015-07-10 04:22:50
β—‹ 2015-11-06 13:20:40
β—‹ 2026-07-26 10:31:54
β—‹CNAMEpres.serverhome.com2017-04-03 β†’ 2017-05-07 Β· 4 obs
● 2017-04-03 21:07:40
● 2017-05-07 16:58:28
β—‹ 2020-04-23 18:58:00
β—‹ 2026-07-26 10:31:54
β—‹CNAMEsnews.serverhome.com2020-04-23 β†’ 2020-04-23 Β· 4 obs
β—‹ 2017-05-07 16:58:28
● 2020-04-23 18:58:00
β—‹ 2026-07-02 12:50:00
β—‹ 2026-07-26 10:31:54

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
vaap.comns1.domainrecover.com, ns2.domainrecover.com2 records

βœ… Authoritative Response

Server:199.247.16.62

NS records: ns1.domainrecover.com, ns2.domainrecover.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vaap.com (unsigned zone)

⏱️ Timing

Total: 316ms | Queries: -

πŸ“„ Records

TypeCountSample Data

πŸ“Œ Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)

Analysis

Name Servers

vaap.com is delegated to two name servers: ns1.domainrecover.com and ns2.domainrecover.com.

vaap.com has the same name server delegation as a number of other domains, such as isoking.com, erohit.com, mystis.com and two more.

At least some of vaap.com's name servers are shared with other domains, for example blocnet.com, aregis.com, nicead.com and two more.

These name servers are often deployed together with the name servers ns1.serverhome.com, ns2.serverhome.com, ns2.servering.com and ns.servering.com.

Each of ns1.domainrecover.com and ns2.domainrecover.com has one IP address: ns1.domainrecover.com uses 149.248.38.58 and ns2.domainrecover.com uses 199.247.16.62.